On 12/07/2016 11:00 AM, Chuck Atkins wrote:
> Shouldn't we be able to accomplish the same same thing with
> just the CMAKE_USE_SYSTEM_FOO variable as a cache entry?
If you can refactor the logic for that then go for it. Note the
`if(CMAKE_BOOTSTRAP)` blocks. IIRC they make the bootstrap
script
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 ca
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 th
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 forc
