Re: [Boost-build] [V2] Testing Tru64 toolset

From: Markus Schöpflin (markus.schoepflin_at_[hidden])
Date: 2006-02-14 10:00:36

Vladimir Prus wrote:

>> Is there a way to achieve this without messing around with a file living
>> _inside_ the boost source tree?
> 
> Yes, create user-config.jam in your home directory (the value of $HOME 
> environment variable), and make all customization there.

Yes, that works.

It seems that BOOST_BUILD_PATH is not searched for this file, is there any 
specific reason for this?

[...]

> Try this:
> 
>  using hp_cxx 
> 	: 65_042_tru64   # version
>     :                # command not specified -- use default
>     :                # options
>     <cflags>"-version V6.5-042"
>     <ldflags>"-version V6.5-042 -use_non_shared_libcxx"
>     ;
> 
> The previous code put options to the second argument -- which is the 'command' 
> argument.

Now it's working, thank you very much for your patience.

So the procedure most regression runners will have to follow is:

1. Create a user-config.jam in their home directory, or wherever this file 
is allowed to live.
2. Add customized toolsets to this file.
3. Use <toolset>-<version1>, <toolset>-<version2>, ... instead of using 
<customized toolset 1>, <customized toolset 2>, ... when running the 
regression tests.

I just started a boost regression run using bbv2, it will take some days to 
complete. When it's finished I will do another run using bbv1 and then try 
to compare the results. We'll see how this fares.

Markus