Boost Testing :
From: Hartmut Kaiser (hartmut.kaiser_at_[hidden])
Date: 2005-05-25 13:34:31
David Abrahams wrote:
> >> Hum, yeah it does. Is this Boost.Build v1 or v2?
> >> Are you running the build under the NT command prompt or
> under cygwin?
> >> Can you show the command that triggers the error above? It should
> >> follow the error in your bjam output.
> No answers?
I assume the regressions tests are run under the NT command prompt, but I'm
> > Perhaps that's all because I have a <threading>single line in the
> > Jamfile, which lets bjam (V1) call the VC8 compiler with the /MLd
> > command line switch, which isn't supported by VC8 anymore.
> Is there a
> > way to have this <threading>single for all but the vc8 compiler?
> You can put the name of a rule in your requirements. Make
> give the rule an interface like the one below:
> # Normally on Linux, Python is built with GCC. A "poor QOI
> choice" in
> # the implementation of the intel tools prevents the use of
> # intel-linked shared libs by a GCC-built executable unless
> they have
> # been told to use the GCC runtime. This rule adds the requisite
> # flags to the compile and link lines.
> rule python-intel-use-gcc-stdlib ( toolset variant :
> non-defaults * )
> if ( ! $(PYTHON_WINDOWS) )
> && ( ! <define>BOOST_PYTHON_STATIC_LIB in $(non-defaults) )
> && [ MATCH (intel) : $(toolset) ]
> return <stdlib>gcc ;
> return ;
Thanks for this explanation.
> But really we should make sure that the msvc toolset doesn't
> do anything with <threading>single when the version is >= 8.
Agreed. But since I don't know boost build enough I'm not able to make this