Re: [jamboost] b-jam build scripts... pass 2...

From: David Abrahams (dave_at_[hidden])
Date: 2002-11-11 08:15:47

Rene Rivera <grafik666_at_[hidden]> writes:

> Recent changes... this is pass 2.
>
> Among many fixes the differences from pass 1 are:
>
> * Per Dave's suggestion the bootstrap scripts (build.bat, and build.sh) can
> be used for the build-to-develop task, not just the build-to-install task.
> The differences are below...
>
> * build.jam, now understand the "--debug" option. This builds the binary
> targets with as much debug info as possible. Including not just debug
> symbols, but also turning optimizations off, and inclusion of profile debug
> info. The debug version is built to a different directory than the release
> so that one can test both release and debug at without interference.
>
> * build.jam, now take "--toolset=<name>" instead of the variable version
> "-sBOOST_JAM_TOOLSET=<name>". So the command for build-to-develop is for
> example:
> ./bootstrap.gcc/jam0 --toolset=gcc --debug
>
> * Both build.bat and build.sh changed so that arguments past the first (or
> the first on if the first is an option) are passed to jam0 so that one can
> do this:
> ./build.sh gcc --debug
> Which bootstraps, and builds the debug version for gcc. Or...
> ./build.sh --debug
> Which guesses the toolset, and builds the debug. Or...
> ./build.sh -- dist
> Which guesses the toolset, builds the release, and packages the distribution
> files. Although there are some build bugs that I have to resolve in this one
> case :-(
>
> * Rewrote most of build.bat :-) So now it can do things like check the PATH
> for executables and check the arguments for options to pass along. Right now
> only the borland check does anything interesting with the PATH, but if you
> have bcc32 in your path it should find it at least for bootstrap.
>
> The bad news... I looked at reading values from the Windows registry and
> this is hard enough to make it useless. There is only one readily available
> way to read them but it means a sequence like:
> regedit-export--->file--->grep/findstr--->unicode2ascii--->filter-into-BAT

Oh, don't worry about that. Rene, this is fabulous! The only thing
missing I think is a documentation page which describes all this. Or
have you gone ahead and done that as well?

-- 
David Abrahams
dave_at_[hidden] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution