Browse Source

CMake: make it possible to use <PackageName>_ROOT to locate dependencies.

next
Vladimír Vondruš 3 years ago
parent
commit
c83c1fcc4f
  1. 5
      CMakeLists.txt
  2. 4
      doc/python/pages/changelog.rst

5
CMakeLists.txt

@ -36,6 +36,11 @@ endif()
if(POLICY CMP0071)
cmake_policy(SET CMP0071 NEW)
endif()
# Allow <PackageName>_ROOT to be used on 3.12+ to point to per-package install
# locations that find_package(PackageName) subsequently picks up
if(POLICY CMP0074)
cmake_policy(SET CMP0074 NEW)
endif()
# Superprojects can use just set(MAGNUM_WITH_BLAH ON) without FORCE CACHE on
# 3.13+
if(POLICY CMP0077)

4
doc/python/pages/changelog.rst

@ -80,6 +80,10 @@ Changelog
Travis banned everyone from using their CI and so all Linux and macOS
builds were migrated from Travis to Circle CI. See also
:gh:`mosra/magnum#350` and :gh:`mosra/magnum#523`.
- It's now possible to use ``<PackageName>_ROOT`` to point to install
locations of dependencies such as Corrade on CMake 3.12+, in addition to
putting them all together inside ``CMAKE_PREFIX_PATH``. See also
:gh:`mosra/magnum#614`.
- On CMake 3.16 and newer, ``FindMagnumBindings.cmake`` can provide
additional details if some component is not found
- The Homebrew package now uses ``std_cmake_args`` instead of hardcoded build

Loading…
Cancel
Save