godotengine/godot-docs
1
0
Fork 0
mirror of https://github.com/godotengine/godot-docs.git synced 2026-01-05 22:09:56 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #7582 from Calinou/scons-update-lto-parameter

Browse Source
This commit is contained in:
Max Hilbrunner
2023-07-22 17:38:21 +02:00
committed by GitHub
parent b9983afb01 338c1f6351
commit abaf08ee1a
4 changed files with 5 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
contributing/development/compiling/compiling_for_linuxbsd.rst
View File

@@ -270,7 +270,7 @@ Manager.
SCons options ``target=template_release production=yes``.
If you are compiling Godot with GCC, you can make the binary
even smaller and faster by adding the SCons option ``use_lto=yes``.
even smaller and faster by adding the SCons option ``lto=full``.
As link-time optimization is a memory-intensive process,
this will require about 7 GB of available RAM while compiling.

2
contributing/development/compiling/compiling_for_windows.rst
View File

@@ -153,7 +153,7 @@ dependencies. Running it will bring up the Project Manager.
SCons option ``target=template_release``.
If you are compiling Godot with MinGW, you can make the binary
even smaller and faster by adding the SCons option ``use_lto=yes``.
even smaller and faster by adding the SCons option ``lto=full``.
As link-time optimization is a memory-intensive process,
this will require about 7 GB of available RAM while compiling.

2
contributing/development/compiling/optimizing_for_size.rst
View File

@@ -79,7 +79,7 @@ and MSVC compilers:
::
scons p=windows target=template_release use_lto=yes
scons p=windows target=template_release lto=full
Linking becomes much slower and more RAM-consuming with this option,
so it should be used only for release builds:

10
contributing/development/debugging/using_cpp_profilers.rst
View File

@@ -29,14 +29,8 @@ To get useful profiling information, it is **absolutely required** to use a Godo
build that includes debugging symbols. Official binaries do not include debugging
symbols, since these would make the download size significantly larger.
To get profiling data that best matches the production environment, you should
compile binaries with the following SCons options:
- For editor binaries: ``target=editor use_lto=yes``
- For debug export templates: ``target=template_debug use_lto=yes``
- For release export templates: ``target=template_release debug_symbols=yes``
- ``debug_symbols=yes`` is required as export templates are stripped from debugging symbols by default.
To get profiling data that best matches the production environment (but with debugging symbols),
you should compile binaries with the ``production=yes debug_symbols=yes`` SCons options.
It is possible to run a profiler on less optimized builds (e.g. ``target=template_debug`` without LTO),
but results will naturally be less representative of real world conditions.