Hi,
one thing that has bothered me in earlier CMake versions is how targets
with imported dependencies are exported. Consider this contrived case:
add_library(yaml SHARED IMPORTED)
set_target_properties(yaml PROPERTIES IMPORTED_LOCATION /usr/lib/libyaml.so)
set_target_properties(yaml PROPERTIES
Philipp Möller wrote:
It would be great, if I could export imported targets and if CMake could
walk the dependency tree automatically and import those targets on an
as-needed basis.
Part of the problem is that the place where you import your dependent
targets from (and the locations
.. and whenever possible the FindXXX.cmake should defined imported targets.
Jc
On Thu, Mar 6, 2014 at 9:38 AM, Philipp Möller bootsare...@gmail.comwrote:
Stephen Kelly steve...@gmail.com writes:
Philipp Möller wrote:
It would be great, if I could export imported targets and if CMake
Jean-Christophe Fillion-Robin
jchris.filli...@kitware.com writes:
.. and whenever possible the FindXXX.cmake should defined imported targets.
This has been another big problem I encountered while trying to fully
targetify my build system: find_package files just aren't up to speed
yet. I was
Philipp Möller wrote:
Stephen Kelly steve...@gmail.com writes:
Philipp Möller wrote:
It would be great, if I could export imported targets and if CMake could
walk the dependency tree automatically and import those targets on an
as-needed basis.
Part of the problem is that the place where
Stephen Kelly steve...@gmail.com writes:
Philipp Möller wrote:
Stephen Kelly steve...@gmail.com writes:
Philipp Möller wrote:
It would be great, if I could export imported targets and if CMake could
walk the dependency tree automatically and import those targets on an
as-needed basis.
