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)
>
> However, if the librar
> 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
> understand the need for the r
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 dep
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
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:
includ