diff options
author | Gregor Jasny <gjasny@googlemail.com> | 2017-01-15 22:23:31 (GMT) |
---|---|---|
committer | Brad King <brad.king@kitware.com> | 2017-01-20 18:51:48 (GMT) |
commit | 10c9c73d58b481a212d1ed87ceeb227a7654bc56 (patch) | |
tree | 10c5baf3611792fe4d3da861bca31e29b6075491 /Copyright.txt | |
parent | fe8e00f6b91d7e8614af5a5ffb2ab68775b06e1c (diff) | |
download | CMake-10c9c73d58b481a212d1ed87ceeb227a7654bc56.zip CMake-10c9c73d58b481a212d1ed87ceeb227a7654bc56.tar.gz CMake-10c9c73d58b481a212d1ed87ceeb227a7654bc56.tar.bz2 |
Xcode: Control emission of EFFECTIVE_PLATFORM_NAME
When building with multiple SDKs within one project Xcode requires
the usage of ${EFFECTIVE_PLATFORM_NAME} to put temporary and build
outout into separate directories. For example an iOS device and
simulator build use two different SDKs (iphoneos and iphonesimulator).
In the past cmake tries to detect embedded toolchains that could
possibly use simulators and emitted EFFECTIVE_PLATFORM_NAME (EPN)
at the proper locations. In #16253 Mark noticed that if he
uses macosx and iphoneos in combination the necessary EPN is not
emitted. This is because CMake by default assumes macosx SDK which
does not trigger EPN emission.
The fist naive approach - enabling EPN unconditionally revealed that
then the EPN leaks into generator expressions like $<TARGET_FILE:xxx>
which might be a regression and thus is unacceptable.
The next approach was to add an CMake property to enable EPN emission
unconditionally. This solved the reported problem.
But the EPN leakage also happened for the embedded toolchains already
without anyone noticing. So the control property was turned into a
tri-state one:
* No definition: EPN is activated for embedded toolchains like before
* ON: EPN is always emitted
* OFF: EPN is never emitted
That approach gives the user the chance to disable EPN for embedded
toolchains and restores generator expression functionality for those.
Closes: #16253
Diffstat (limited to 'Copyright.txt')
0 files changed, 0 insertions, 0 deletions