From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-02-26 07:21:49
On Wednesday 22 February 2006 09:17, Noel Belcourt wrote:
> > using gcc : 4.0.2 : /usr/local/gcc-4.0.2/bin/g++.exe ;
> > using gcc : 3.4.4 ; # this one is what you get when you just say
> > # "gcc" at the command line.
> > using gcc : 4.0.0 : /usr/local/gcc-4.0.0/bin/g++.exe ;
> > using gcc : 2.95 : /bin/g++-2.exe ;
> This solution would be ideal if, on our other systems, the paths to the
> compilers, linkers, and communication libraries were known and fixed.
> Unfortunately the paths are only known each time we login and load the
> necessary modules as sysadmin can and does move the installations
> around with regularity. Since we can't use the above solution we're
> reduced to using bjam to build for a single toolset at a time on those
> systems, which really isn't a problem.
> I'll definitely use this technique for the systems we control though.
How about creating a script for each g++ version, in some location you
control, for example, in /home/noel/local/bin/g++-4.0.2.
The script would contain:
and then given the path to this script in "using"?
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