Hey again Marcel, Your reply got me thinking. I just checked again, and found that I just have to set the LIBRARY_PATH correctly as well. After that everything seems to work. Apparently this was not done in the right way. Since I have to use PATH anyway to find the FoobarConfig.cmake files, it is just as easy to also set LIBRARY_PATH to find the dependencies of the already compiled libraries. The problem was that PATH was already set in the right way, so I didn't notice that LIBRARY_PATH was not set correctly.
Anyhow, the thing that ultimately confused me in such a way that I thought the problem was somewhere else was that https://cmake.org/cmake/help/v3.0/command/link_directories.html says that find_package should return *absolute* paths, which it does not, since it just returns the targets. Maybe that can be cleared up a bit to prevent further confusion. Thanks a lot for pointing me in the right direction! Cheers, Sven -- 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
