From: David Abrahams (david.abrahams_at_[hidden])
Date: 2001-11-27 07:35:05
----- Original Message -----
From: "joerg.walter" <jhr.walter_at_[hidden]>
> > system should work two ways:
> > 1. The user executes all of the setup scripts for tools she uses before
> > invoking the build system, which clutters the environment with lots of
> > for each toolset.
> > 2. The user points the system (on the command-line, in a site-config.jam
> > user-config.jam, or in the environment) at the installation directories
> > the toolsets, and the build system does the rest.
> I checked this and found a difficulty, which excludes 2. for
> intel-linux-tools.jam IMO: iccvars.sh changes pathes to point to shared
> libraries. If one uses 2. the execution of regression tests in
> $(BOOST_ROOT)/status will fail. So intel-linux-tools.jam currently
I think you should look again at metrowerks-tools.jam. Build actions can
have multiple lines; if properly set up, the corresponding script is called
before the tool is invoked. You could do the same with iccvars.sh.
> > Once again, please have a look at BOOST_ROOT/status/Jamfile.
> As far as I currently understand, $(BOOST_ROOT)/status/Jamfile builds and
> executes regression tests. But which Jamfile builds other library specific
None, I guess. Often the examples are part of the regression tests (or at
least they should be)...
> > * Slowness
> Didn't really notice that ;-)
In the status Jamfile things are pretty slow.
> > * Inflexibility (dealing with multiple compiler versions, target
> > * Difficulty of maintenance
> Partly due to jam itself?
Partly, but that's why I've been adding features like crazy ;-)
Now that it's done, I think the language is a lot stronger.
> > * Difficulty of setup
> > And then there are some really cool things we could do which we're not
> > currently doing:
> > _And_Installation
> I'll have a look at it.
Please also browse through the main Boost.Build Wiki page and associated
(when the site is reachable again ;-))
> Best regards
> P.S.: I'll attach the current intel-linux-tools.jam.
Sorry to keep coming back to you with this, but if you could try to get the
invocation of iccvars.sh into each action, I will check in your toolset
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