[CMake] FindBoost: FIND_PACKAGE ( Boost COMPONENTS filesystem )

[Philip Lowman]

Personally, I think FindBoost is complex enough without having to  also keep
track of boost's internal dependencies as well.  Maybe things would be
better if the boost people published this info with every release.

If you'd like to check in support for the feature and volunteer to maintain
it, however, that's fine by me.  It would make so much more sense to do
within Boost itself,  though.

On Nov 4, 2009 11:54 AM, "Marcel Loose" <loose at astron.nl> wrote:

Hi Philip,

I've been following this thread with interest. Your solution puts the
burden on the (ignorant) end-user's shoulders. How is that poor
developer going to solve the pre/post version 1.34 issue, which is a
Boost-internal issue? In an ideal world, Boost would provide the
FindBoost.cmake file, or would generate the BoostConfig.cmake file.

Anyway, IMHO this really should be solved in FindBoost.cmake. One
possible way to make maintenance less of a burden is to define Boost's
(version-dependent) inter-dependencies once in FindBoost.cmake and let
the macro resolve these dependencies. Something like:

set(Boost_filesystem_DEPENDENCIES)
set(Boost_wave_DEPENDENCIES)
set(Boost_serialization_DEPENDENCIES filesystem)   # Just assuming
# Assume filesystem depends on system for Boost > 1.34

if(${_boost_maj}.${_boost_min} VERSION_GREATER 1.34)
 list(APPEND Boost_filesystem_DEPENDENCIES system)
endif()
# Assume wave depends on system for Boost > 1.36
if(${_boost_maj}.${_boost_min} VERSION_GREATER 1.36)
 list(APPEND Boost_wave_DEPENDENCIES system)
endif()

Does that make any sense?

Best regards,
Marcel Loose.

On Wed, 2009-11-04 at 11:14 -0500, Philip Lowman wrote: > Mathieu, > > It's
a nice idea, but give...

> _______________________________________________ > Powered by
www.kitware.com > > Visit other Kitw...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20091104/f2a4567e/attachment.htm>