mirror of
https://github.com/Kitware/CMake.git
synced 2026-05-07 22:59:56 -05:00
Eugene Shalygin
a2e9fe38e4
Add a `CMAKE_REQUIRE_FIND_PACKAGE_<PackageName>` variable is complement to `CMAKE_DISABLE_FIND_PACKAGE_<PackageName>` with just the opposite behaviour: it turns non-required find_package call into the required one. While optional package dependencies usually result in simple and clean build logic, sometimes people want to be sure those optional dependencies will be found and used. Examples are reproducible builds and build instructions for 3rd parties. People choose to make find_package calls REQUIRED and put them behind an option(). Such workarounds blend build logic with build environment management and do not look elegant.
12 lines
483 B
Plaintext
12 lines
483 B
Plaintext
CMake Error at RequiredOptionValuesClash.cmake:4 \(find_package\):
|
|
find_package for module Foo was made REQUIRED with
|
|
CMAKE_REQUIRE_FIND_PACKAGE_Foo but CMAKE_DISABLE_FIND_PACKAGE_Foo is
|
|
enabled. A REQUIRED package cannot be disabled.
|
|
Call Stack \(most recent call first\):
|
|
CMakeLists.txt:3 \(include\)
|
|
+
|
|
CMake Error at RequiredOptionValuesClash.cmake:5 \(message\):
|
|
This error must not be reachable\.
|
|
Call Stack \(most recent call first\):
|
|
CMakeLists.txt:3 \(include\)
|