diff options
author | Daniele E. Domenichelli <daniele.domenichelli@iit.it> | 2013-07-08 12:37:23 (GMT) |
---|---|---|
committer | Daniele E. Domenichelli <daniele.domenichelli@iit.it> | 2013-07-10 13:06:01 (GMT) |
commit | 07b44e7a1f3facf3b4300fb98bfa0705ef728bce (patch) | |
tree | 8515e648934ff08a0e37ada3bc7f9aba09e170dd /Tests/CMakeOnly/SelectLibraryConfigurations | |
parent | a18e9586dbd7172911fde22b6b6331676b817e4d (diff) | |
download | CMake-07b44e7a1f3facf3b4300fb98bfa0705ef728bce.zip CMake-07b44e7a1f3facf3b4300fb98bfa0705ef728bce.tar.gz CMake-07b44e7a1f3facf3b4300fb98bfa0705ef728bce.tar.bz2 |
SelectLibraryConfigurations: Do not cache the _LIBRARY variable
SelectLibraryConfigurations module currently cache and mark as advanced
the variable ${basename}_LIBRARY.
${basename}_LIBRARY_RELEASE and ${basename}_LIBRARY_DEBUG are usually
cached, because they often come from find_library().
${basename}_LIBRARY on the other hand is always of type
"optimized;${${basename}_LIBRARY_RELEASE};debug;${${basename}_LIBRARY_DEBUG}"
or just "${basename}_LIBRARY_RELEASE" or "${basename}_LIBRARY_DEBUG" if
only one version of the library is not found, if both have the same
value, or if configuration types are not supported.
Caching and marking as advanced just ${basename}_LIBRARY_RELEASE and
${basename}_LIBRARY_DEBUG is enough, just by modifying these two
variables, the user has enough control on finding the library, and
having 3 variables is redundant and confusing.
Diffstat (limited to 'Tests/CMakeOnly/SelectLibraryConfigurations')
0 files changed, 0 insertions, 0 deletions