From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2008-05-25 01:07:55
>> However at the moment, I must admit I do not see why Boost Build has
>> not been implemented so that it builds all of its projects in the same
>> build folder, without splitting them over separate project specific
>> build folders. That would make the initial example work 'the good way'
>> even with multiple projects.
> I don't understand this. How would you distinguish between debug and
> release builds, between Parser.obj and Parser.obj of two different
> projects if all of those were in the same folder??
I did not mean placing build results for different build
into a single folder. They would still each get their own folder. I just
considered using the same build folder for the same configuration of
I.e. If you build projects A & B in debug & release variants, you now
but this suggestion would make them be built in:
On the other hand, I have managed to get some sleep since I wrote
that and now I see that then multiple projects would then be restricted
to not being able to have source file with different content but using
the same name.
Hope I have not managed to mess up the explanation again... :-)
There is a different topic of whether to maintain that folder as we
do now or perhaps use just use a SHA-1 hash of the used property set and
not organize the build folders hierarchically. This would help avoid the
problem with build folder paths becoming too long for some projects and
hitting the OS path size limit.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk