summaryrefslogtreecommitdiffstats
path: root/Modules/CMakeFindDependencyMacro.cmake
Commit message (Collapse)AuthorAgeFilesLines
* find_dependency: Give more helpful message if VERSION is emptyAurélien Gâteau2014-03-131-2/+5
|
* find_dependency: Make sure invalid EXACT use can be reported.Stephen Kelly2014-03-111-3/+3
| | | | | | Test the first argument directly for matching 'EXACT'. The error check in its previous position was incorrect and would only trigger with a version of '0' or similar.
* find_dependency: Don't propagate EXACT argument.Stephen Kelly2014-03-061-2/+11
| | | | | | | | If a package is requested with an EXACT version, that doesn't imply that dependencies must be found EXACTly too. Extend the macro to allow specifying that a dependency must be found by EXACT version instead.
* find_dependency: unset cmake_fd_version variable at end of macroAlex Merry2014-02-261-0/+1
| | | | This matches the other macro variables.
* find_dependency: use correct version variable nameAlex Merry2014-02-261-1/+1
| | | | The code set cmake_fd_version, but used ${version}.
* find_dependency: Ensure that ARGV1 has valid local contentStephen Kelly2014-02-241-1/+4
| | | | | The ARGV1 value could come from a wrapping context if find_dependency is called from a function.
* find_dependency: Add namespacing for variables in the macro.Stephen Kelly2014-02-241-13/+17
| | | | Avoid setting a variable called 'version' etc.
* Always set version variable of find_dependency macroAlex Merry2014-02-231-3/+1
| | | | | | | | | | | If there is no ARGV1, that is fine; version will be made empty, and no version will be passed to find_package(). This is relevant when find_dependency is invoked multiple times, sometimes with a version specified and sometimes without. find_dependency(dep1 3.4) find_dependency(dep2) # version still set to 3.4.
* FeatureSummary: Don't list transitive package dependenciesStephen Kelly2014-02-031-0/+9
| | | | | | | | | | | | | | Set a global property in the find_package implementation. Track and reset that property in the find_dependency macro. Read the property in FeatureSummary when determining whether to print output. This means that packages which are found only as dependencies are not listed by FeatureSummary, but if a project uses find_package elsewhere directly, then it will be listed by FeatureSummary. Suggested-by: Alex Merry http://thread.gmane.org/gmane.comp.kde.devel.frameworks/10640
* Split the find_dependency macro into a separate file.Stephen Kelly2013-12-131-0/+58
This allows Config file authors to use it without having to use CONFIGURE_PACKAGE_CONFIG_FILE.
generated by cgit v0.12 at 2024-09-01 01:20:36 (GMT)