diff options
| author | Brad King <brad.king@kitware.com> | 2016-02-05 19:18:01 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2016-02-05 19:43:16 (GMT) |
| commit | 1b9d15c1e7adff5170f10d488483e1dc4e99d507 (patch) | |
| tree | b191064ac37e028602be180c5ba9107e22cb536f /Tests/RunCMake/Syntax/BracketNoSpace4-result.txt | |
| parent | a5a5a6857241c21d306661d723b749839f4c6e1a (diff) | |
| download | CMake-1b9d15c1e7adff5170f10d488483e1dc4e99d507.zip CMake-1b9d15c1e7adff5170f10d488483e1dc4e99d507.tar.gz CMake-1b9d15c1e7adff5170f10d488483e1dc4e99d507.tar.bz2 | |
ExternalProject: Be compatible with projects setting CMAKE_CFG_INTDIR
Since commit v3.5.0-rc1~32^2~1 (ExternalProject: Simplify `cmake
--build` configuration passing, 2016-01-19) we use the `$<CONFIG>`
generator expression to generate the `cmake --build . --config <config>`
value for the default BUILD_COMMAND instead of the CMAKE_CFG_INTDIR
placeholder value provided by multi-config generators. However, some
projects have been abusing the old implementation detail by setting
CMAKE_CFG_INTDIR themselves to get a specific configuration. Those
projects should be updated to set their own BUILD_COMMAND to get
non-default behavior. Meanwhile we can be compatible with their
existing releases by detecting when CMAKE_CFG_INTDIR is not a
generator-provided placeholder and using its value instead.
Diffstat (limited to 'Tests/RunCMake/Syntax/BracketNoSpace4-result.txt')
0 files changed, 0 insertions, 0 deletions