|
Boost Testing : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-03-20 04:40:20
Martin Wille wrote:
>> How do you do this now? If you send me all the files that configure
>> different python versions for different toolsets, I'll come up with a
>> appropriate V2 setup.
>
> I do this by running the tests for one toolset at a time.
> Each of the toolset definition has its own python setup.
>
> I can't use a global setup in v1, either, because v1 doesn't allow for
> toolset-specific python setup, AFAIK. This has been talked about a few
> times on this list or on the BB list.
Oh, I did not see those messages.
> Of course, I could try to use a different test-config.jam files for each
> toolset, respectively. But that would basically mean I'd have to
> re-create the mess that I now have for v1 testing.
>
> What I currently use for v1 works like this:
......
> If there's no way to integrate different Python setups into a single
> file in v2 then I'll go the one-file-per-toolset route. However, in that
> case, it would be *very* helpful if regression.py would honour my
> BOOST_BUILD_PATH setting instead of overwriting it.
At the moment, Python can't be configured per-toolset, but this should be
easy to add. I hope to get something working later today, and will get back
to you then.
- Volodya