From: Bill Hoffman (bill.hoffman_at_[hidden])
Date: 2007-10-16 22:22:34
David Abrahams wrote:
> IIUC you mix two different jobs in that step (not necessarily a bad
> thing): system introspection and identification of build resources
> (what autoconf does) and translation of medium-level target
> descriptions (not high-level ones, though Doug's layer begins to
> approach that) into low-level ones.
>> then you can build lots of times. With bjam it does the configure
>> and build all at once.
> yes, the autoconf part is a cost bjam users pay every time, although
> writing very specific "using" statements in user-config.jam can remove
> much of that cost because Boost.Build mostly assumes that the user
> giving specific instructions (e.g. about tool paths) knows what he's
With the KDE project, I think many of the performance gains over the
scons build system were because of the way cmake separates the configure
stage from the build stage. CMake would of course runs faster if you
give it more information about tool paths as well. It does not look
for stuff if you tell it exactly where to find it.
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