Boost Testing :
From: Martin Wille (mw8329_at_[hidden])
Date: 2005-06-23 03:27:20
David Abrahams wrote:
> Martin Wille writes:
>>include $(BOOST_ROOT)/tools/build/v1/gcc-stlport-tools.jam ;
> The line above is the wrong way to go about things. Why aren't you
> extends-toolset gcc-stlport ;
> all other such toolsets do?
Because the language used in Jamfiles was a mystery to me when I wrote
that (mostly, it is still a mystery to me).
You may get away with it in this
> case, but it's a hack.
It works fine for me, since I only run tests for one toolset at a time.
We'll, hopefully, switch to BBv2 soon; I don't think I need to fix my
toolset definitions now.
One example for mysteries: I used 'extends-toolset' for the intel-based
toolsets. However, while I was able to use 'local' for a couple of
variables, I wasn't able to use it for PYTHON_ROOT. Hence, the
intel-7.1-linux toolset reads:
local INTEL_LINUX_VERSION = "70" ;
local INTEL_LINUX_ROOT = "/usr/local/icc-7.1/compiler70" ;
PYTHON_ROOT = "/usr/local/Python-2.2.3-intel" ;
extends-toolset intel-linux ;
Send instant messages to your online friends http://au.messenger.yahoo.com