On Tue, 16 May 2017 12:32:11 -0700 Pawel Veselov <pawel.vese...@gmail.com> wrote:
> > I was once in a situation where I could have used pkg-config with a > > custom path to have pkg-config look for the .pc-file. I then > > switched to find_library with the custom-path slightly adapted and > > it worked at least as good as with pkg-config, if not better. For > > my case. > > Right. My reason of preferring pkg-config is because it may have all > other kind of stuff in it that the maintainer thought is necessary. > I'd imagine some .pc files export a boatload of flags for all 3 > stages, and I rather not ignored them. It is also quite important > when there are chained dependencies. Understandable. If I understand things correctly, pkg-config does not return the RPATH-arguments necessary to link with. IOW, if used in a GNU Makefile you would also need to add these by yourself, right? So your problem is not a cmake-problem. If this is the case, what you're looking for is a macro/script which transforms -l and -L-arguments to the fully-qualified filename. That should be doable with a combination of string(SUBSTRING) and find_library() - if you dare ;-) . > AFAIU, find_library() is not > capable of tracking down dependencies. No, find_library only returns the (complete) filename of a library found via its arguments. -- Patrick. -- 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