On 17 June 2015 at 22:58, Stephen Kelly <steve...@gmail.com> wrote: > Klaim - Joël Lamotte wrote: > > > Thinking about boost, if package files works well with header-only > > libraries (which I > > suppose it should as long as the boost define header-only targets) > > then it would be very useful indeed. > > Yes, I wrote some cmake 3.0 features specifically for the Boost use cases > (header only and lots of cyclic dependencies). > > > Then I have to have all my libraries to link with all the boost libraries > > listed in the boost > > library variable generated by FindBoost. > > I don't have working knowledge of FindBoost, so I can't give a good answer. > The documentation at the top of the file says it creates a variable per > library though. > > Yes it seems that I missed that part when I worked on it, totally my mistake.
> > If I understand correctly, if FindBoost was supporting imported targets > > and using "Boost" as a > > namespace (like Qt does), then I could link my libraries to boost > > libraries in a more > > precise way as I would link each library separately instead of everything > > FindBoost > > put in the boost libraries variable. > > This still has other advantages anyway, such as transitivity, conciseness, > consistency, better error messages etc. > > Thanks, > > Steve. >
-- 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
