Subject: Re: [boost] Boost Modularization: did we get it right?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2012-05-09 11:11:55
On 05/09/2012 06:31 AM, Mathias Gaunard wrote:
> On 05/09/2012 03:17 PM, Oliver Kowalke wrote:
>>>>> I'm annoyed that I get some additonal burden to re-write this stuff
>>>>> the new build env again because the old one will not work with the
>>>>> modularized boost.
>>>> Once you have run the script, the usual Boost.Build system will work
>>> And I've just done that and it did work and the test did pass.
>>> Windows 7 with VC++ 10.0.
>> And why not provide a wrapper that let the other developers use the
>> old build env with modularized boost?
> Boost.Build *is* "the old build env".
> I've suggested to the people in charge of modularization to integrate
> the script within Boost.Build itself, so that this step is done
It's a little bit tricky to make
this work. If we hard link or
copy each header, then Boost.Build
can handle it trivially, but Jam's
#include scanner currently has no
way to search sym-linked directories
that are created as part of the build.
Actually, we could do a recursive
glob of the target directory and
make the all the headers in the
directory outputs of the sym-link
action. Then it should just work.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk