summaryrefslogtreecommitdiffstats
path: root/Help/release
diff options
context:
space:
mode:
authorEugene Shalygin <eugene.shalygin@gmail.com>2021-07-07 12:41:34 (GMT)
committerBrad King <brad.king@kitware.com>2021-07-08 12:03:38 (GMT)
commita2e9fe38e43bd73513cde410f83e53e0c31ec6d6 (patch)
tree5967cc1531f5a4f5c561c6d1159c9a98db434036 /Help/release
parentd49b507bb6fb798bdab3edc738af80495efa979f (diff)
downloadCMake-a2e9fe38e43bd73513cde410f83e53e0c31ec6d6.zip
CMake-a2e9fe38e43bd73513cde410f83e53e0c31ec6d6.tar.gz
CMake-a2e9fe38e43bd73513cde410f83e53e0c31ec6d6.tar.bz2
find_package: Add variable to make package REQUIRED
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.
Diffstat (limited to 'Help/release')
-rw-r--r--Help/release/dev/find_package-required-var.rst5
1 files changed, 5 insertions, 0 deletions
diff --git a/Help/release/dev/find_package-required-var.rst b/Help/release/dev/find_package-required-var.rst
new file mode 100644
index 0000000..36935ef
--- /dev/null
+++ b/Help/release/dev/find_package-required-var.rst
@@ -0,0 +1,5 @@
+find_package-required-var
+-------------------------
+
+* The :variable:`CMAKE_REQUIRE_FIND_PACKAGE_<PackageName>` variable was added
+ to turn a non-REQUIRED :command:`find_package` call into a REQUIRED one.