kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Help: Remove disadvantage creating IMPORTED targets in Find modules. 

An IMPORTED target in either type of package can equally depend on
an IMPORTED target in a Find module, which must be found as a
dependency, which is presumably the problem being implied.  This is
not a distinction of creating an IMPORTED target in a Find module.
This commit is contained in:
Stephen Kelly 2014-12-04 23:25:56 +01:00
parent 169f116632
commit b96b025b2a
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Help/manual/cmake-developer.7.rst
View File

@ -733,10 +733,7 @@ The more modern approach is to behave as much like
``<package>Config.cmake`` files as possible, by providing imported ``<package>Config.cmake`` files as possible, by providing imported
targets. As well as matching how ``*Config.cmake`` files work, the targets. As well as matching how ``*Config.cmake`` files work, the
libraries, include directories and compile definitions are all set just libraries, include directories and compile definitions are all set just
by using the target in a :command:`target_link_libraries` call. The by using the target in a :command:`target_link_libraries` call.
disadvantage is that ``*Config.cmake`` files of projects that use
imported targets from find modules may require more work to make sure
those imported targets that are in the link interface are available.
In either case (or even when providing both variables and imported In either case (or even when providing both variables and imported
targets), find modules should provide backwards compatibility with old targets), find modules should provide backwards compatibility with old