Re: [Boost-testing] V2 switch: Martin Wille

From: Martin Wille (mw8329_at_[hidden])
Date: 2006-03-20 03:46:46

Hi,

Vladimir Prus wrote:
> Martin Wille wrote:
> 
> 
>>Vladimir Prus wrote:

[...]
>>>Speaking about python, example line is:
>>>
>>>    using python : 2.3 : C:/python ;
>>
>>
>>Uhm, that won't work. I need to be able to specify different python
>>paths for different toolsets.
> 
> 
> 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.

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:

# gcc-3.2.3-linux.jam uses the distribution's Python installation
GCC_ROOT_DIRECTORY = /usr/local/gcc-3.2.3 ;
include $(TOOLSET_PATH)"/gcc-limited.jam" ;

# gcc-4.0.3-linux-tools.jam uses a gcc 4 bases Python installation
GCC_ROOT_DIRECTORY = /usr/local/gcc-4.0.3 ;
flags gcc DEFINES : _GLIBCXX_DEBUG=1 ;
PYTHON_ROOT = /usr/local/python/2.4/gcc-4.0.0 ;
PYTHON_VERSION = 2.4 ;
include $(TOOLSET_PATH)"/gcc-limited-pthread.jam" ;

# other gcc-x.y.z-linis-tools.jam files look similarly

# gcc-limited-pthread.jam adds some common options
# and provides fallback for Python
PYTHON_ROOT ?= /usr ;
PYTHON_VERSION ?= 2.3 ;
GXX = g++wrap --limit-memory=600 --limit-cpu=1800 -pthread ;
include $(BOOST_ROOT)/tools/build/v1/gcc-tools.jam ;

# Setup for the intel compilers used to be even more of a mess.
# intel-8.0-linux-tools.jam
{
         local INTEL_LINUX_VERSION = "80" ;
         local INTEL_LINUX_ROOT = "/opt/intel_cc_80" ;

         #PYTHON_ROOT = "/usr/local/Python-2.2.3-intel" ;
         #include $(BOOST_ROOT)"/tools/build/v1/intel-linux-tools.jam" ;

         extends-toolset intel-linux ;
}

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.

Regards,
m
Send instant messages to your online friends http://au.messenger.yahoo.com