summaryrefslogtreecommitdiffstats
path: root/CMakeLogo.gif
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2019-01-29 16:54:46 (GMT)
committerBrad King <brad.king@kitware.com>2019-01-30 13:00:06 (GMT)
commit95210d027a03192532fcf2c71c98c79fd4cc0fd1 (patch)
treebc44de663aba125b071d57b73cbab0ccdc0cc4e6 /CMakeLogo.gif
parent62c0b1aebb827fc8a133cedfa343322d28714501 (diff)
downloadCMake-95210d027a03192532fcf2c71c98c79fd4cc0fd1.zip
CMake-95210d027a03192532fcf2c71c98c79fd4cc0fd1.tar.gz
CMake-95210d027a03192532fcf2c71c98c79fd4cc0fd1.tar.bz2
macOS: Restore compatibility for setting FRAMEWORK after install()
The `FRAMEWORK` target property affects the way the `install()` command treats the target and so should be set first. Our implementation assumed that this was always the case and led to an assertion failure. Prior to CMake 3.12 this was visible only when using an explicit `LIBRARY ... NAMELINK_ONLY` option, but commit 0212d7c762 (install: add NAMELINK_COMPONENT argument, 2018-04-18, v3.12.0-rc1~139^2~3) made it possible with a simple `LIBRARY DESTINATION`. Fully supporting out-of-order specification will require non-trivial refactoring to defer install generator creation to generate time. For now simply restore the old behavior of installing the framework to the library destination and warn about the case. Fixes: #18848
Diffstat (limited to 'CMakeLogo.gif')
0 files changed, 0 insertions, 0 deletions