From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-02-16 07:10:58
On Tuesday 14 February 2006 18:00, Markus Schöpflin wrote:
> 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?
It fact, it should search BOOST_BUILD_PATH. That how it find the one inside
Boost.Build tree in case where there's no in $HOME.
> > 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.
Yes, and I've tried to document that on:
> 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.
Will be interesting to see.
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