diff options
| author | Brad King <brad.king@kitware.com> | 2017-09-13 13:29:15 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2017-09-13 13:37:30 (GMT) |
| commit | c5b5bb270f54dab4ff529688a26ea8aa271fa0e1 (patch) | |
| tree | 667a60287a6cdfc51e8578c512fb0b71d187407a /CTestCustom.cmake.in | |
| parent | ffa164736ec78f27583ca4515ff3dfc7a82fc702 (diff) | |
| download | CMake-c5b5bb270f54dab4ff529688a26ea8aa271fa0e1.zip CMake-c5b5bb270f54dab4ff529688a26ea8aa271fa0e1.tar.gz CMake-c5b5bb270f54dab4ff529688a26ea8aa271fa0e1.tar.bz2 | |
VS: Do not consider MAP_IMPORTED_CONFIG_<CONFIG> on non-imported targets
Since commit v3.9.0-rc1~309^2 (include_external_msproject: Honor
MAP_IMPORTED_CONFIG_<CONFIG>, 2017-04-04) we accidentally honor
`MAP_IMPORTED_CONFIG_<CONFIG>` while generating the `.sln` file entries
for normal targets. This causes `devenv.com`-driven builds to use the
mapping incorrectly for normal targets. Check that a target really
comes from `include_external_msproject` before considering the map.
Furthermore, when we do use the map, we should only take the first entry
if more than one configuration is specified. Otherwise we end up giving
VS a configuration name with a `;` in it.
Fixes: #17276
Diffstat (limited to 'CTestCustom.cmake.in')
0 files changed, 0 insertions, 0 deletions