As requested here: #1230 (comment) . Ping @hebasto
Among other things this allows us to link against object libraries.
3.13 has been mentioned several times as a good overlap between newish features and widespread Linux availability.
As requested here: #1230 (comment) . Ping @hebasto
Among other things this allows us to link against object libraries.
3.13 has been mentioned several times as a good overlap between newish features and widespread Linux availability.
208 | - # See: https://cmake.org/cmake/help/latest/policy/CMP0063.html 209 | - cmake_policy(SET CMP0063 NEW) 210 | -endif() 211 | +# Honor visibility properties for all target types. 212 | +# See: https://cmake.org/cmake/help/latest/policy/CMP0063.html 213 | +cmake_policy(SET CMP0063 NEW)
I was going by the docs:
This policy was introduced in CMake version 3.3. CMake version 3.26.0-rc6 warns when the policy is not set and uses OLD behavior. Use the cmake_policy() command to set it to OLD or NEW explicitly.
Is that not what happens in practice?
CMake version 3.26.0-rc6 warns when the policy is not set and uses OLD behavior.
Is that not what happens in practice?
CMake will emit such a warning.
https://cmake.org/cmake/help/latest/command/cmake_minimum_required.html#policy-settings:
The
cmake_minimum_required(VERSION)command implicitly invokes thecmake_policy(VERSION)command...
All policies known to the running version of CMake and introduced in the
<min>... version or earlier will be set to useNEWbehavior.
Oh, I see...
"use the cmake_policy() explicitly" vs "implicitly invokes the cmake_policy()" -- indeed confusing :D
Thanks for the explanation, fixed.
Concept ACK.
Among other things this allows us to link against object libraries.
ACK 96dd0625112672e841eea723398cc2a1c3489a30
utACK 96dd0625112672e841eea723398cc2a1c3489a30