Shouldn't we be able to accomplish the same same thing with just the CMAKE_USE_SYSTEM_FOO variable as a cache entry? I ran into this when trying to build CMake master and I want to use all system libraries but librhash. Given the current implementation, there's a number of configurations that cause no way to actually set this with the user-facing option. Typically I'd do -DCMAKE_USE_SYSTEM_LIBRARIES=ON -DCMAKE_USE_SYSTEM_LIBRHASH=OFF but the user-facing option has no meaning because internally the CMAKE_USE_SYSTEM_LIBRARY_RHASH variable, initialized by CMAKE_USE_SYSTEM_LIBRARIES force overrides anything I try to set for it.
---------- Chuck Atkins On Wed, Dec 7, 2016 at 10:33 AM, Brad King <brad.k...@kitware.com> wrote: > On 12/07/2016 10:02 AM, Chuck Atkins wrote: > > 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. > > This is for interaction with the bootstrap script. Options to that > come in as cache entries that set the default for the user-facing > options IIRC. > > -Brad > >
-- 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
