Parallel builds and runs

Vladimir Prus <ghostcs.msu.su> writes:

>> Dave,
>>
>> 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:
>
>    #!/bin/bash
>
>    gcc-select 4.0.2   
>    g++ "$"
>
>
> and then given the path to this script in
"using"?

What's wrong with site-config.jam?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build