Subject: Re: [boost] Boost Modularization: did we get it right?
From: Beman Dawes (bdawes_at_[hidden])
Date: 2012-05-09 08:16:12
On Wed, May 9, 2012 at 7:05 AM, Oliver Kowalke <oliver.kowalke_at_[hidden]> wrote:
>> > so that means that the new build env does not work out of the box?!
>> The new one does. The old one doesn't, and requires you to use the
>> second approach.
>> >> include path or you run a script that generates flattened headers.
>> > nonsense
>> Running a script to make the new setup compatible with the old one is
It would be informative if you would expand your comments beyond one
word replies. Otherwise It is easy to misunderstand what you mean.
Most software packages require some kind of installation process. For
Boost, it has been the "Getting started" process documented on the web
site. With modularization, some of the details of "Getting Started"
will change. Why are you concerned that some of those installation
process details ensures that user and developer scripts and setups
continue to work?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk