Re: [CMake] Should configuration package files define module package variables?

On Sat, Sep 2, 2017 at 3:08 AM, P F wrote: > In general, if the library does not have any dependencies, you can just > export the targets directly to the config.cmake file: > > install(TARGETS foo EXPORT foo-config) > install(EXPORT foo-config DESTINATION lib/cmake/foo) > >

Re: [cmake-developers] [CMake] Should configuration package files define module package variables?

On Sat, Sep 2, 2017 at 3:08 AM, P F wrote: > In general, if the library does not have any dependencies, you can just > export the targets directly to the config.cmake file: > > install(TARGETS foo EXPORT foo-config) > install(EXPORT foo-config DESTINATION lib/cmake/foo) > >

Re: [CMake] Should configuration package files define module package variables?

> On Aug 25, 2017, at 11:21 AM, Robert Dailey wrote: > > So I've been studying the find_package[1] and "creating packages"[2] > documentation, as well as the CMakePackageConfigHelpers[3] page. > > Based on the current offerings of configuration packages, I do not >

Re: [CMake] Should configuration package files define module package variables?

Hi, On Freitag, 25. August 2017 11:21:50 CEST Robert Dailey wrote: > However, what I'm wondering is even though the import targets should > contain all information about include directories, libraries, etc, > should I still define the typical Foo_INCLUDE_DIRS, Foo_LIBRARIES > variables? This

Re: [CMake] Should configuration package files define module package variables?

Doh, forgot the links I intended to reference in my original email: [1]: https://cmake.org/cmake/help/v3.6/command/find_package.html [2]: https://cmake.org/cmake/help/v3.6/manual/cmake-packages.7.html#creating-packages [3]: https://cmake.org/cmake/help/v3.6/module/CMakePackageConfigHelpers.html

[CMake] Should configuration package files define module package variables?

So I've been studying the find_package[1] and "creating packages"[2] documentation, as well as the CMakePackageConfigHelpers[3] page. Based on the current offerings of configuration packages, I do not understand the need for the relocatable config.cmake file when all it really contains is: