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.
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
