<p>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. </p>
<p>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. </p>
<p><blockquote type="cite">On Nov 4, 2009 11:54 AM, "Marcel Loose" <<a href="mailto:loose@astron.nl">loose@astron.nl</a>> wrote:<br><br>Hi Philip,<br>
<br>
I've been following this thread with interest. Your solution puts the<br>
burden on the (ignorant) end-user's shoulders. How is that poor<br>
developer going to solve the pre/post version 1.34 issue, which is a<br>
Boost-internal issue? In an ideal world, Boost would provide the<br>
FindBoost.cmake file, or would generate the BoostConfig.cmake file.<br>
<br>
Anyway, IMHO this really should be solved in FindBoost.cmake. One<br>
possible way to make maintenance less of a burden is to define Boost's<br>
(version-dependent) inter-dependencies once in FindBoost.cmake and let<br>
the macro resolve these dependencies. Something like:<br>
<br>
set(Boost_filesystem_DEPENDENCIES)<br>
set(Boost_wave_DEPENDENCIES)<br>
set(Boost_serialization_DEPENDENCIES filesystem) # Just assuming<br>
# Assume filesystem depends on system for Boost > 1.34<br>
<p><font color="#500050">if(${_boost_maj}.${_boost_min} VERSION_GREATER 1.34)
</font></p> list(APPEND Boost_filesystem_DEPENDENCIES system)<br>
endif()<br>
# Assume wave depends on system for Boost > 1.36<br>
if(${_boost_maj}.${_boost_min} VERSION_GREATER 1.36)<br>
list(APPEND Boost_wave_DEPENDENCIES system)<br>
endif()<br>
<br>
Does that make any sense?<br>
<br>
Best regards,<br>
<font color="#888888">Marcel Loose.<br>
</font><p><font color="#500050">
On Wed, 2009-11-04 at 11:14 -0500, Philip Lowman wrote:
> Mathieu,
>
> It's a nice idea, but give...</font></p><p><font color="#500050">> _______________________________________________
> Powered by <a href="http://www.kitware.com">www.kitware.com</a>
>
> Visit other Kitw...</font></p></blockquote></p>