compiling_for_linuxbsd.rst 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277
  1. .. _doc_compiling_for_linuxbsd:
  2. Compiling for Linux, \*BSD
  3. ==========================
  4. .. highlight:: shell
  5. Requirements
  6. ------------
  7. For compiling under Linux or other Unix variants, the following is
  8. required:
  9. - GCC 7+ or Clang 6+.
  10. - Python 3.5+.
  11. - SCons 3.0+ build system. If your distribution uses Python 2 by default,
  12. or you are using a version of SCons prior to 3.1.2, you will need to change
  13. the version of Python that SCons uses by changing the shebang (the first line)
  14. of the SCons script file to ``#! /usr/bin/python3``.
  15. Use the command ``which scons`` to find the location of the SCons script file.
  16. - pkg-config (used to detect the dependencies below).
  17. - X11, Xcursor, Xinerama, Xi and XRandR development libraries.
  18. - MesaGL development libraries.
  19. - ALSA development libraries.
  20. - PulseAudio development libraries.
  21. - *Optional* - libudev (build with ``udev=yes``).
  22. .. seealso:: To get the Godot source code for compiling, see
  23. :ref:`doc_getting_source`.
  24. For a general overview of SCons usage for Godot, see
  25. :ref:`doc_introduction_to_the_buildsystem`.
  26. Distro-specific one-liners
  27. ^^^^^^^^^^^^^^^^^^^^^^^^^^
  28. +------------------+-----------------------------------------------------------------------------------------------------------+
  29. | **Alpine Linux** | :: |
  30. | | |
  31. | | apk add scons pkgconf gcc g++ libx11-dev libxcursor-dev libxinerama-dev libxi-dev libxrandr-dev \ |
  32. | | libexecinfo-dev |
  33. +------------------+-----------------------------------------------------------------------------------------------------------+
  34. | **Arch Linux** | :: |
  35. | | |
  36. | | pacman -S --needed scons pkgconf gcc libxcursor libxinerama libxi libxrandr mesa glu libglvnd \ |
  37. | | alsa-lib pulseaudio |
  38. +------------------+-----------------------------------------------------------------------------------------------------------+
  39. | **Debian** / | :: |
  40. | **Ubuntu** | |
  41. | | sudo apt-get install build-essential scons pkg-config libx11-dev libxcursor-dev libxinerama-dev \ |
  42. | | libgl1-mesa-dev libglu-dev libasound2-dev libpulse-dev libudev-dev libxi-dev libxrandr-dev |
  43. +------------------+-----------------------------------------------------------------------------------------------------------+
  44. | **Fedora** | :: |
  45. | | |
  46. | | sudo dnf install scons pkgconfig libX11-devel libXcursor-devel libXrandr-devel libXinerama-devel \ |
  47. | | libXi-devel mesa-libGL-devel mesa-libGLU-devel alsa-lib-devel pulseaudio-libs-devel \ |
  48. | | libudev-devel gcc-c++ libstdc++-static libatomic-static |
  49. +------------------+-----------------------------------------------------------------------------------------------------------+
  50. | **FreeBSD** | :: |
  51. | | |
  52. | | sudo pkg install py37-scons pkgconf xorg-libraries libXcursor libXrandr libXi xorgproto libGLU \ |
  53. | | alsa-lib pulseaudio |
  54. | | |
  55. +------------------+-----------------------------------------------------------------------------------------------------------+
  56. | **Gentoo** | :: |
  57. | | |
  58. | | emerge -an dev-util/scons x11-libs/libX11 x11-libs/libXcursor x11-libs/libXinerama x11-libs/libXi \ |
  59. | | media-libs/mesa media-libs/glu media-libs/alsa-lib media-sound/pulseaudio |
  60. +------------------+-----------------------------------------------------------------------------------------------------------+
  61. | **Mageia** | :: |
  62. | | |
  63. | | urpmi scons task-c++-devel pkgconfig "pkgconfig(alsa)" "pkgconfig(glu)" "pkgconfig(libpulse)" \ |
  64. | | "pkgconfig(udev)" "pkgconfig(x11)" "pkgconfig(xcursor)" "pkgconfig(xinerama)" "pkgconfig(xi)" \ |
  65. | | "pkgconfig(xrandr)" |
  66. +------------------+-----------------------------------------------------------------------------------------------------------+
  67. | **OpenBSD** | :: |
  68. | | |
  69. | | pkg_add python scons llvm |
  70. +------------------+-----------------------------------------------------------------------------------------------------------+
  71. | **openSUSE** | :: |
  72. | | |
  73. | | sudo zypper install scons pkgconfig libX11-devel libXcursor-devel libXrandr-devel libXinerama-devel \ |
  74. | | libXi-devel Mesa-libGL-devel alsa-devel libpulse-devel libudev-devel libGLU1 |
  75. +------------------+-----------------------------------------------------------------------------------------------------------+
  76. | **NetBSD** | :: |
  77. | | |
  78. | | pkg_add pkg-config py37-scons |
  79. | | |
  80. | | For audio support, you can optionally install ``pulseaudio``. |
  81. +------------------+-----------------------------------------------------------------------------------------------------------+
  82. | **Solus** | :: |
  83. | | |
  84. | | sudo eopkg install -c system.devel scons libxcursor-devel libxinerama-devel libxi-devel \ |
  85. | | libxrandr-devel mesalib-devel libglu alsa-lib-devel pulseaudio-devel |
  86. +------------------+-----------------------------------------------------------------------------------------------------------+
  87. Compiling
  88. ---------
  89. Start a terminal, go to the root dir of the engine source code and type:
  90. ::
  91. scons -j8 platform=linuxbsd
  92. A good rule of thumb for the ``-j`` (*jobs*) flag, is to have at least as many
  93. threads compiling Godot as you have cores in your CPU, if not one or two more.
  94. Feel free to add the ``-j`` option to any SCons command you see below.
  95. You can automatically use all available CPU cores with command substitution.
  96. On Linux, you can use ``nproc``:
  97. ::
  98. scons -j$(nproc)
  99. On \*BSD, you can use ``sysctl -n hw.ncpu``:
  100. ::
  101. scons -j$(sysctl -n hw.ncpu)
  102. .. note::
  103. Prior to Godot 4.0, the Linux/\*BSD target was called ``x11`` instead of
  104. ``linuxbsd``. If you are looking to compile Godot 3.x, make sure to use the
  105. `stable branch of this documentation <https://docs.godotengine.org/en/stable/development/compiling/compiling_for_x11.html>`__.
  106. If all goes well, the resulting binary executable will be placed in the
  107. "bin" subdirectory. This executable file contains the whole engine and
  108. runs without any dependencies. Executing it will bring up the project
  109. manager.
  110. .. note::
  111. If you wish to compile using Clang rather than GCC, use this command:
  112. ::
  113. scons platform=linuxbsd use_llvm=yes
  114. Using Clang appears to be a requirement for OpenBSD, otherwise fonts
  115. would not build.
  116. .. note:: If you are compiling Godot for production use, then you can
  117. make the final executable smaller and faster by adding the
  118. SCons option ``target=release_debug``.
  119. If you are compiling Godot with GCC, you can make the binary
  120. even smaller and faster by adding the SCons option ``use_lto=yes``.
  121. As link-time optimization is a memory-intensive process,
  122. this will require about 7 GB of available RAM while compiling.
  123. .. note:: If you want to use separate editor settings for your own Godot builds
  124. and official releases, you can enable
  125. :ref:`doc_data_paths_self_contained_mode` by creating a file called
  126. ``._sc_`` or ``_sc_`` in the ``bin/`` folder.
  127. Compiling a headless/server build
  128. ---------------------------------
  129. To compile a *headless* build which provides editor functionality to export
  130. projects in an automated manner, use::
  131. scons -j8 platform=server tools=yes target=release_debug
  132. To compile a debug *server* build which can be used with
  133. :ref:`remote debugging tools <doc_command_line_tutorial>`, use::
  134. scons -j8 platform=server tools=no target=release_debug
  135. To compile a *server* build which is optimized to run dedicated game servers,
  136. use::
  137. scons -j8 platform=server tools=no target=release
  138. Building export templates
  139. -------------------------
  140. .. warning:: Linux binaries usually won't run on distributions that are
  141. older than the distribution they were built on. If you wish to
  142. distribute binaries that work on most distributions,
  143. you should build them on an old distribution such as Ubuntu 16.04.
  144. You can use a virtual machine or a container to set up a suitable
  145. build environment.
  146. To build Linux or \*BSD export templates, run the build system with the
  147. following parameters:
  148. - (32 bits)
  149. ::
  150. scons platform=linuxbsd tools=no target=release bits=32
  151. scons platform=linuxbsd tools=no target=release_debug bits=32
  152. - (64 bits)
  153. ::
  154. scons platform=linuxbsd tools=no target=release bits=64
  155. scons platform=linuxbsd tools=no target=release_debug bits=64
  156. Note that cross-compiling for the opposite bits (64/32) as your host
  157. platform is not always straight-forward and might need a chroot environment.
  158. To create standard export templates, the resulting files in the ``bin/`` folder
  159. must be copied to:
  160. ::
  161. $HOME/.local/share/godot/templates/[gd-version]/
  162. and named like this (even for \*BSD which is seen as "Linux/X11" by Godot):
  163. ::
  164. linux_x11_32_debug
  165. linux_x11_32_release
  166. linux_x11_64_debug
  167. linux_x11_64_release
  168. However, if you are writing your custom modules or custom C++ code, you
  169. might instead want to configure your binaries as custom export templates
  170. here:
  171. .. image:: img/lintemplates.png
  172. You don't even need to copy them, you can just reference the resulting
  173. files in the ``bin/`` directory of your Godot source folder, so the next
  174. time you build, you automatically have the custom templates referenced.
  175. Using Clang and LLD for faster development
  176. ------------------------------------------
  177. You can also use Clang and LLD to build Godot. This has two upsides compared to
  178. the default GCC + GNU ld setup:
  179. - LLD links Godot significantly faster compared to GNU ld or gold. This leads to
  180. faster iteration times.
  181. - Clang tends to give more useful error messages compared to GCC.
  182. To do so, install Clang and the ``lld`` package from your distribution's package manager
  183. then use the following SCons command::
  184. scons platform=linuxbsd use_llvm=yes use_lld=yes
  185. After the build is completed, a new binary with a ``.llvm`` suffix will be
  186. created in the ``bin/`` folder.
  187. It's still recommended to use GCC for production builds as they can be compiled using
  188. link-time optimization, making the resulting binaries smaller and faster.
  189. Using Pyston for faster development
  190. -----------------------------------
  191. You can use `Pyston <https://www.pyston.org/>`__ to run SCons. Pyston is a JIT-enabled
  192. implementation of the Python language (which SCons is written in). It is currently
  193. only compatible with Linux. Pyston can speed up incremental builds significantly,
  194. often by a factor between 1.5× and 2×. Pyston can be combined with Clang and LLD
  195. to get even faster builds.
  196. - Download the `latest portable Pyston release <https://github.com/pyston/pyston/releases/tag/pyston_2.3.2>`__.
  197. - Extract the portable ``.tar.gz`` to a set location, such as ``$HOME/.local/opt/pyston/`` (create folders as needed).
  198. - Use ``cd`` to reach the extracted Pyston folder from a terminal,
  199. then run ``./pyston -m pip install scons`` to install SCons within Pyston.
  200. - To make SCons via Pyston easier to run, create a symbolic link of its wrapper
  201. script to a location in your ``PATH`` environment variable::
  202. ln -s ~/.local/opt/pyston/bin/scons ~/.local/bin/pyston-scons
  203. - Instead of running ``scons <build arguments>``, run ``pyston-scons <build arguments>``
  204. to compile Godot.
  205. If you can't run ``pyston-scons`` after creating the symbolic link,
  206. make sure ``$HOME/.local/bin/`` is part of your user's ``PATH`` environment variable.