On Mon, 29 Feb 2016 21:20:59 +0100
Stephen Kelly wrote:
> Patrick Boettcher wrote:
>
> > I came across the INTERFACE-type of libraries when writing a
> > FindModule.cmake-file for custom libraries installed by my
> > project.
>
> You don't provide FindModules for your
Patrick Boettcher wrote:
> I came across the INTERFACE-type of libraries when writing a
> FindModule.cmake-file for custom libraries installed by my
> project.
You don't provide FindModules for your CMake-built libraries.
See
https://cmake.org/cmake/help/v3.4/manual/cmake-packages.7.html
On 02/29/2016 04:06 PM, Clément Gregoire wrote:
Speaking of imported targets, I'm wondering why alias imported targets
aren't added to all default FindXXX.cmake scripts. This would help
provide better examples, and have the community use better
cmakelists.txt and hopefully reduce the bad
Speaking of imported targets, I'm wondering why alias imported targets
aren't added to all default FindXXX.cmake scripts. This would help provide
better examples, and have the community use better cmakelists.txt and
hopefully reduce the bad usages of include_directories and such
Le lun. 29 févr.
On 02/29/2016 03:34 PM, Patrick Boettcher wrote:
Hi list,
I came across the INTERFACE-type of libraries when writing a
FindModule.cmake-file for custom libraries installed by my
project.
Here is what I'm doing after having found the libraries and the
determined the paths: LIB1 is the library
Hi list,
I came across the INTERFACE-type of libraries when writing a
FindModule.cmake-file for custom libraries installed by my
project.
Here is what I'm doing after having found the libraries and the
determined the paths: LIB1 is the library and LIB1_INCLUDE_DIRS its
include-dirs: