On May 16, 2007, at 12:46 PM, Dean Michael Berris wrote:
On 5/16/07, David Abrahams <dave@boost-consulting.com> wrote:
on Sun May 13 2007, "Dean Michael Berris" <dmberris-AT- friendster.com> wrote:
I guess the thought of using something not-Boost maintained is brought about by the obvious hardships in maintaining .jam files in Boost.Build itself, and extending the tool chain as well as the mere maintenance of the code to fight fires and squash bugs that seem to be never ending.
Yup. Even with the new Getting Started Guide, just take a look at the number of complaints we've had on the user's list about being unable to build Boost 1.34. So far these are largely issues having to do with configuring the tools.
Someone (John Maddock I think) suggested we use something like a ./configure script which actually configured BBv2 for you -- i.e. edited your site-config.jam and/or user-config.jam file setting the correct/detected/configured toolkits. Might be worth looking at, and might even be interactive (Python anyone? ;) ).
I wrote such a script, and it's there in $BOOST_ROOT. It only works on Unix-like systems, but it handles the simplest cases very well. - Doug