Re: [boost] how to specify options for Boost-building?

Subject: Re: [boost] how to specify options for Boost-building?
From: Oliver Kullmann (O.Kullmann_at_[hidden])
Date: 2009-02-12 14:12:40

> 
> > Unfortunately, it seems that, different from all other build systems I'm aware of,
> > bjam doesn't print out a summary of what it will be doing. I tried many variations of
> > syntax, but apparently it never worked out.
> 
> No build system I know produces summary of that it *will* be doing. Some build systems echo
> the commands before executing them, but definitely not all -- for example, CMake does not
> print complete commands either. You can make Boost.Build to print commands using -d2 option.
>

I didn't mean the build-system as such, but the concrete instance: For example building
CLisp I get a summary: Here are all the instructions you gave as (and as we understand them!),
here are our findings about your system, and here is what we are going to do.

>
> http://www.boost.org/boost-build2/doc/html/bbv2/advanced/invocation.html

Thanks for this information! This page is valuable.

Now I activated more informative output via

-d+2 --debug-configuration --debug-building

(not clear what I really need), and I see

notice: [cmdline-cfg] Detected command-line request for gcc-4.1.2: toolset= gcc version= 4.1.2
notice: [cmdline-cfg] toolset gcc-4.1.2 not previously configured; attempting to auto-configure now
notice: will use 'g++' for gcc, condition <toolset>gcc-4.1.2
notice: using gcc libraries :: <toolset>gcc-4.1.2 :: /usr/local/bin /usr/local/lib /usr/local/lib32 /usr/local/lib64

This is definitely not what I want:

So the remaining open problems is how to get my *local* gcc working?
Apparently

 --toolset=gcc-4.1.2
 --toolset-root=PATH-TO-LOCAL-INSTALLATION
 --"-sGCC_ROOT_DIRECTORY=PATH-TO-LOCAL-INSTALLATION"

which used to work for boost 1_34_1, is no longer working.

According to 

http://www.boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html

all what I need to do instead seems to tell bjam the full path to my g++ (and then
apparently it figures out the rest): Can this information be passed as a parameter,
or is such a .jam-file needed?
 
> > 3) No python; this seems also unproblematic
> > (but apparently it vanished from the documentation?)
> > 
> >  --without-python
> 
> It is present in "--help" output.
> 

But it "python" a library?

Thanks!

Oliver