diff options
author | Fred Baksik <frodak17@gmail.com> | 2019-04-08 13:55:35 (GMT) |
---|---|---|
committer | Fred Baksik <frodak17@gmail.com> | 2019-04-11 17:15:51 (GMT) |
commit | 83c47ef5b8a6b1a63edbd82092d8eae68da453d6 (patch) | |
tree | 1521a0a54e76fab9fd0fd4e7d6c3867b59a40db6 /Source/cm_codecvt.hxx | |
parent | 5d2e1404bdfa83eeae5b361bd7d8a882aadc7242 (diff) | |
download | CMake-83c47ef5b8a6b1a63edbd82092d8eae68da453d6.zip CMake-83c47ef5b8a6b1a63edbd82092d8eae68da453d6.tar.gz CMake-83c47ef5b8a6b1a63edbd82092d8eae68da453d6.tar.bz2 |
GHS: Update project layout to accommodate gbuild inconsistencies
-- Do not use reference projects, use build hierarchy instead.
gbuild has three parallel levels:
* low -- Parallelizes compiling source files within a single project (.gpj)
file when safe to do so.
* medium -- Parallelizes processing files within a single linked output when
safe to do so.
* high [default] -- Parallelizes processing files whenever safe to do so,
including linking task.
Testing showed that for some combinations of gbuild / MULTI there are issues
with building a project that uses references to target project files along with
using {nobuild} option.
Sometimes the archiving of a library and linking of an executable were
happening in parallel and the build would fail when linking because the
archive wasn't complete.
This behavior was also inconsistent when running the build from MULTI and
from the command line with gbuild. In some cases MULTI did not parallelize
archiving and linking, but gbuild performed these actions in parallel.
The parallel build issue was not seen when using a build hierarchy where the
project listed the project files normally instead of using a reference link.
The other option was to add the -parallel_level=medium to the command line
when using "cmake --build" but this wouldn't fix the issue if gbuild itself
was used to and the user might not be aware of the extra option used by cmake.
Diffstat (limited to 'Source/cm_codecvt.hxx')
0 files changed, 0 insertions, 0 deletions