The FooBarConfig.cmake is something that should be generated by FooBar's
build. The reason you don't get absolute paths for the "libraries" from a
package config file is that they're not actually libraries but imported
targets. The imported target let's you treat "foo" as though it were a
library built by your project. It then has the appropriate target
properties set on it ti define the full path to it's library, etc. That
being said, if you're manually creating the FooBarConfig.cmake that's not
really the right approach. If the FooBar buil;d doesn't actually generate
it's own FooBarConfig.cmake file then you'll want to create you're own
FindFooBar.cmake. A bare bones find module that creates an imported target
would look something like this:
if(NOT FooBar_FOUND AND NOT TARGET FooBar::FooBar)
find_path(FooBar_INCLUDE_DIR FooBar.h)
find_library(FooBar_LIBRARY FooBar)
include(FindPackageHandleStandardArgs)
find_package_handle_standard_args(FooBar
FOUND_VAR FooBar_FOUND
REQUIRED_VARS FooBar_INCLUDE_DIR FooBar_LIBRARY
)
endif()
if(FooBar_FOUND AND NOT TARGET FooBar::FooBar)
add_library(FooBar::FooBar UNKNOWN IMPORTED)
set_target_properties(FooBar::FooBar PROPERTIES
IMPORTED_LOCATION ${FooBar_LIBRARY}
INTERFACE_INCLUDE_DIRECTORIES ${FooBar_INCLUDE_DIR}
)
endif()
Then in your project you can use:
find_package(FooBar)
add_library(MyLib supercoolfiles.cxx)
target_libkLibraries(MyLib FooBar::FooBar)
Where this starts to get really helpful in your situation is if you have an
imported target for A, B, and C, then you can create the appropriate
dependencies. Say, for example, you have a FindA.cmake that follows the
pattern above and generates an A::A target. Then in your FindB.cmake you
can have:
if(NOT B_FOUND AND NOT TARGET B::B)
find_path(B_INCLUDE_DIR B.h)
find_library(B_LIBRARY B)
include(FindPackageHandleStandardArgs)
find_package_handle_standard_args(B
FOUND_VAR B_FOUND
REQUIRED_VARS B_INCLUDE_DIR B_LIBRARY
)
* find_package(A QUIET) if(A_FOUND) set(B_Extra_Deps A::A) endif()*
endif()
if(B_FOUND AND NOT TARGET B::B)
add_library(B::B UNKNOWN IMPORTED)
set_target_properties(B::B PROPERTIES
IMPORTED_LOCATION ${B_LIBRARY}
INTERFACE_INCLUDE_DIRECTORIES ${B_INCLUDE_DIR}
)
* if(B_Extra_Deps) set_target_properties(B::B PROPERTIES
INTERFACE_LINK_LIBRARIES ${B_Extra_Deps} ) endif()*
endif()
and similarly for FindC.cmake. Since A::A, B::B, and C::C are actual
proper CMake targets and not just library files then they carry with them
associated target dependency information. In CMake vernacular we refer
this as "target usage requirements" since the target caries with it all the
necessary information for something to actually use it, whether that's just
extra link libraries or also extra include directories and compile
definitions needed. The Package::Target naming convention is the idea that
each package has it's own namespace where you may define multiple targets.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
