forked from bartvdbraak/blender
0d43d0bcab
Many modern computers support a lot of threads (parrallel building jobs), but are somewhat restricted in memory, when some building jobs can require several GB each. Ninja builder has pools, which extend the usual `-j X` make parallelizing option, by allowing to specify different numbers of parallel jobs for different targets. This commit defines three pools, one for linking, one for usual compile, and one for compiling some 'heavy' cpp libs, when a single file can require GB of RAM in full debug builds. Simply enabling WITH_NINJA_POOL_JOBS will try to set default sensible values for those three pools based on your machine specifications, you can then tweak further the values of NINJA_MAX_NUM_PARALLEL_ settings, if you like. On my system (8 cores, 16GB RAM), it allows to build a full debug with all ASAN options build with roughly 7GB of RAM used at most, pretty much as quickly as without that option (which would require up to 11GB of available RAM at some points). Review task: D4780. |
||
|---|---|---|
| .. | ||
| config | ||
| example_scripts | ||
| Modules | ||
| platform | ||
| buildinfo.cmake | ||
| clang_array_check.py | ||
| cmake_consistency_check_config.py | ||
| cmake_consistency_check.py | ||
| cmake_netbeans_project.py | ||
| cmake_print_build_options.py | ||
| cmake_qtcreator_project.py | ||
| cmake_static_check_clang_array.py | ||
| cmake_static_check_cppcheck.py | ||
| cmake_static_check_smatch.py | ||
| cmake_static_check_sparse.py | ||
| cmake_static_check_splint.py | ||
| macros.cmake | ||
| packaging.cmake | ||
| project_info.py | ||
| project_source_info.py | ||
| RpmBuild.cmake | ||