
on Tue May 15 2007, Bernhard Fischer <rep.dot.nop-AT-gmail.com> wrote:
On Mon, May 14, 2007 at 11:04:56PM -0600, David Abrahams wrote:
It's not your fault for following the pattern that was already there, but looking at the path to identify the compiler is suboptimal at best. We should be invoking the compiler using the SHELL function and asking it to tell us its version. See gcc.jam for an example.
Does gcc.jam pickup CC and CXX env variables, btw?
No.
I think that i had trouble to use the auto guessed toolset since i want to use the CC and CXX and do not have gcc nor g++. I had to create my own cc.jam, since for --with-toolset=cc i was unable to find a corresponding jam file. CC and CXX both point to gcc executables of the form gcc-4.2-suffix resp. g++-etc
How would i use these compilers to build boost?
Create a user-config.jam file in your home directory where you have import toolset.using ; using gcc : 4.2-<suffix> : <command that invokes g++-4.2-suffix> ; which might look just like: import toolset.using ; using gcc : 4.2-mysuf : g++-4.2-mysuf ; Then you can build with --toolset=gcc-4.2-mysuf HTH, -- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com