summaryrefslogtreecommitdiffstats
path: root/Tests/RunCMake/find_package/RunCMakeTest.cmake
Commit message (Collapse)AuthorAgeFilesLines
* find_*: Use debug logging infrastructureRobert Maynard2019-12-191-0/+1
| | | | | | Teach the find_package, find_library, find_program, find_path, and find_file commands to print debug log messages when enabled by the `--debug-find` command-line option or `CMAKE_FIND_DEBUG_MODE` variable.
* FindPackage: Support `NO_[]_PATH` global call optionsRobert Maynard2019-07-221-0/+2
|
* find_package: add test coverage for CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKSDavid Aguilar2019-01-161-0/+3
|
* find_package(): Add policy to remove the FindQt moduleKyle Edwards2018-11-141-0/+3
| | | | | | | | Removing FindQt.cmake gives Qt upstream a path forward to export its own QtConfig.cmake files which can be found by find_package() without having to explicitly specify CONFIG. Projects that still want to use Qt3/4 can call find_package(Qt[34]), include(FindQt), or add FindQt.cmake to their CMAKE_MODULE_PATH.
* find_package: Use PackageName_ROOT variables as search prefixesBrad King2018-03-161-0/+2
| | | | | | | | | | | | | | | | | | | This feature was originally added by commit v3.9.0-rc1~71^2~2 (find_*: Add a new PackageRoot search path group, 2017-05-03) and documented by commit v3.9.0-rc1~71^2 (find_*: Add docs for PackageRoot search path group, 2017-05-03). However, we had to disable the feature and remove the documentation in commit v3.9.1~2^2 (find_*: Disable the PACKAGE_ROOT search path group for CMake 3.9, 2017-08-08) due to breaking projects that used `PackageName_ROOT` variables themselves. Add policy `CMP0074` to restore the `PackageName_ROOT` variable behavior in a compatible way. Also revise the stack of root paths to store the paths themselves rather than the package names. This way the policy can be considered at the `find_package` call site instead of individual `find_` calls inside a find module. Co-Author: Chuck Atkins <chuck.atkins@kitware.com> Issue: #17144
* find_package: Split PACKAGE_ROOT tests to work with smaller regexChuck Atkins2017-08-021-0/+2
|
* find_package: Restore longer message when config files were consideredBrad King2017-07-071-0/+2
| | | | | | | | | | | | | | | | | | Since commit v3.9.0-rc1~58^2 (find_package: shorten output for missing package in config mode, 2017-05-09) we print only the one line - Could NOT find Foo (missing: Foo_DIR) when package Foo cannot be found in CONFIG mode and it is not REQUIRED. However, in the case that package configuration files were found but not used, this one line message leaves out important information. This can happen when a package configuration file sets `Foo_FOUND` to `FALSE` or when its package version file does not match the requested version. Restore the longer message in these cases. Otherwise a seemingly valid explicit `Foo_DIR` setting appears to be silently ignored even if it was considered. Fixes: #17029
* find_*: Add tests for PackageRoot search path groupChuck Atkins2017-05-161-0/+1
|
* Tests: Add case for package version file unmatched policy scopeBrad King2015-11-241-0/+2
|
* find_package: Test rejection of required+optional componentsBrad King2012-03-191-0/+1
|
* find_package: additional test for checking the error messageAlex Neundorf2012-03-131-0/+1
| | | | | | | | This patch adds a test which checks the error message, which is produced in the case that a Config file has set Foo_FOUND to FALSE by itself. Alex
* Use generalized RunCMake test infrastrucure for find_package testBrad King2012-03-121-0/+14