From: cboostwill (will_at_[hidden])
Date: 2005-08-21 19:30:30
We are using a number of Boost libraries already in our projects.
We are now writing apps. for inhouse use we plan to offer later to
the gnu/linux crowd. There is pressure on me to use the standard gnu
make/automake tools as they produce the standard tar balls used by
Gnu/Linux distros to make their packages.
I read that jam was autoconf compatible, but querying this list's
archives, this does not seem trivial. I have found a utility called
autojam that allows one to use automake with jam; I have figured out
how to use an extension of make(makepp) for project management, while
using autotools on the resulting code for our gnu/linux standard tar
Boost.jam looks like my best choice for project management. My
only concern here is delivery. Also note that I am not saying that
using the full blown boost.jam build methods without any autotools is
totally out of the question for delivery, but that would be REALLY
hard to sell to my people. It's hard enough arguing to not rely on
make.("What do you mean make isn't good for large projects; it's what
they use for the Linux kernel...").
I am spending a couple more days researching this, and I will post
my conclusions, but opinions from this community would be appreciated
as I continue to sift through this.
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