Skip to content

Linux Build Instructions

int edited this page Oct 28, 2020 · 29 revisions

NOTE: The Linux build is still under development on another fork, and is currently being drafted to merge (see PR #486) - don't expect stability of any kind.

Dependencies (libraries must be i686/lib32):

  • make
  • Clang/LLVM
  • automake
  • autoconf

Libraries:

  • libunwind
  • glibc
  • freetype
  • fontconfig
  • libGL
  • libX11
  • openal
  • libncurses
  • libcurl-gnutls

Note: If you get an error in compiling due to -lcurl-gnutls being missing, you need a symlink:

sudo ln -s /usr/lib32/libcurl-gnutls.so.4 /usr/lib32/libcurl-gnutls.so

This occurs on Arch/pacman based distros as far as we know.

Instructions:

  1. Make sure the path leading up to team-comtress-2 has no spaces in it. This will lead to errors compiling the third party libraries.
  2. Prepare for unforeseen consequences; crashes during compilation aren't common but should be expected.
  3. Run ./build.sh -l to compile. This can take any amount of time; it took 20 minutes on a Ryzen 5 1600.
  4. To make sure it compiled correctly, run it again. If you see no errors, then it compiled. Success!
  5. Run ./link.sh to symlink your TF2 assets into the ../game folder. You will get some 'errors' complaining about files already existing; that is normal.
  6. In the main repository directory, run ./run.sh to launch the game. If you have mangohud installed, this will also launch.

Bug reports are appreciated! Please send a full backtrace by running with LLDB and crashing - run.sh -d will launch lldb with the game. Once in LLDB at the terminal, enter r at the (lldb) prompt to run the game, then reproduce the crash. The game should freeze instead of quitting and in your terminal, LLDB should say what the error was, and be at another prompt. type bt to get a backtrace, and put it in an issue on HurricanePootis's fork with how you got there.

Also: Build time in seconds should be reported after build.sh is done the first time you run it (the first line should say real then a number). Reporting your successful build time with your hardware in an issue (if you need to make one) could also be helpful.

Clone this wiki locally