|
Boost Users : |
From: David Abrahams (dave_at_[hidden])
Date: 2006-02-03 14:05:33
"Drumheller, Michael" <michael.drumheller_at_[hidden]> writes:
> Main stumbling point for me was bjam. It's not so much of a problem for
> building the libraries themselves--you don't need to know anything about
> it at all, really. But when you start building your own extensions, it
> would be helpful to have a dozen or so examples of really basic
> operations, like changing the destination directory, defining a
> preprocessor macro on the compiler command line, stuff like that.
>
> I have to say, I'm almost embarrassed to be writing this, because it
> seems like nobody on this list ever complains about bjam. So maybe it's
> just me. But to me, bjam is an incomprehensible monster, a big YALITTC
> (yet-another-link-in-the-tool-chain) that just makes it harder to sell
> boost within an organization.
It's not just you. We need to make Boost.Build more comprehensible
and easier to use. If nobody else steps up I'm probably going to end
up rewriting all the documentation once we officially switch to
Boost.Build version 2.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net