[cmake-developers] Building CMake system libraries
Chuck Atkins
chuck.atkins at kitware.com
Wed Dec 7 10:02:56 EST 2016
What's the use case for the various ways to use a system version of a
dependency in CMake's build? There seems to be CMAKE_USE_SYSTEM_LIBRARIES
for initializing all of them and then CMAKE_USE_SYSTEM_LIBRARY_FOO to
override that but then also the user-facing option CMAKE_USE_SYSTEM_FOO
which is force-set to CMAKE_USE_SYSTEM_LIBRARY_FOO. I'm trying to
understand why there's both CMAKE_USE_SYSTEM_LIBRARY_FOO and
CMAKE_USE_SYSTEM_FOO when it seems that the user-facing option
CMAKE_USE_SYSTEM_FOO isn't usually settable. Wouldn't it feasible to just
have the user-facing CMAKE_USE_SYSTEM_FOO and not deal with the seperate
CMAKE_USE_SYSTEM_LIBRARY_FOO?
----------
Chuck Atkins
Staff R&D Engineer, Scientific Computing
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20161207/8daee3c6/attachment.html>
More information about the cmake-developers
mailing list