| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This matches the other macro variables.
|
|
|
|
| |
The code set cmake_fd_version, but used ${version}.
|
|
|
|
|
| |
The ARGV1 value could come from a wrapping context if find_dependency
is called from a function.
|
|
|
|
| |
Avoid setting a variable called 'version' etc.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
This allows Config file authors to use it without having to use
CONFIGURE_PACKAGE_CONFIG_FILE.
|