[cmake-developers] [PATCH 5/5] FindBoost.cmake: Add Boost::boost and Boost::<C> targets and documentation

[Philipp Moeller]

Stephen Kelly <steveire at gmail.com> writes:

> Philipp Moeller wrote:
>
>> Stephen Kelly <steveire at gmail.com> writes:
>
>>> The wiki page is out of date, and so is the repo, because boost is trying
>>> to make a release before finishing the modularization work and it is all
>>> on- hold for several more months.
>> 
>> This project has been going on for ages and considering how long it took
>> Boost to change their SCM or the (stalled?) ryppl and 0install efforts I
>> don't see this happening anytime soon.
>
> Indeed. Until a few weeks ago I believed the effort was permanently aborted. 
> Then some Boost people starting doing the modularization work, but were 
> asked to stop until after the next release (I don't know the details of that 
> reasoning). 
>
> After the major part of the modularization TODO is done, it would be viable 
> to start talking about whether they want to use cmake, and if not, teaching 
> bjam to create cmake config packages. 
>
> As you note, this is several months away. As far as I know, they want to 
> make their release in early August, but I have no idea what blocks that or 
> if it is likely that they will reach that target.
>
> I'm just noting all of this for informational purposes :).
>
>>> This means:
>>>
>>>  1) Creating a Boost::boost monolithic target may not be appropriate
>> 
>> IMO, even a modularized boost build should provide a target that just
>> gives you all of the includes for convenience in addition to more
>> fine-grained access, but I see why one would think otherwise.
>
> In a modularized system, "all" of boost might not be there, and the parts 
> that are might be in different places.

Sorry, poor wording on my part. I meant to say a target for "all" of
boost that is available. It should be easy to support includes in
different locations by just having the Boost::includes target consist of
dependencies on Boost::component_includes targets.

This is of course contrary to what modularization is supposed to
achieve, but sometimes a little convenience helps adoption a lot.