CMake

Commit Graph

Author	SHA1	Message	Date
Alex Merry	5878c5d919	Always set version variable of find_dependency macro 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.	2014-02-23 11:31:30 +01:00
Stephen Kelly	a6971f6510	FeatureSummary: Don't list transitive package dependencies 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	2014-02-03 20:20:42 +01:00
Stephen Kelly	20cafa2e1f	Split the find_dependency macro into a separate file. This allows Config file authors to use it without having to use CONFIGURE_PACKAGE_CONFIG_FILE.	2013-12-13 16:14:02 +01:00

Author

SHA1

Message

Date

Alex Merry

5878c5d919

Always set version variable of find_dependency macro

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.

2014-02-23 11:31:30 +01:00

Stephen Kelly

a6971f6510

FeatureSummary: Don't list transitive package dependencies

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

2014-02-03 20:20:42 +01:00

Stephen Kelly

20cafa2e1f

Split the find_dependency macro into a separate file.

This allows Config file authors to use it without having to use
CONFIGURE_PACKAGE_CONFIG_FILE.

2013-12-13 16:14:02 +01:00

3 Commits