Boost Testing :
From: David Abrahams (dave_at_[hidden])
Date: 2005-05-25 13:16:42
Hartmut Kaiser <hartmut.kaiser_at_[hidden]> writes:
> David Abrahams wrote:
>> > I don't see any change, and I don't understand this
>> "manifest" stuff either.
>> Me neither, but Microsoft assures me that it's neccessary to
>> do it when I build DLLs. I have no idea why it should be
>> failing. The command I was given by Microsoft supposedly
>> extracts the manifest from the DLL and then processes it somehow.
>> > it almost looks like the test framework is attempting to invoke
>> > the ........manifest file directly
>> 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.
> 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 ;
But really we should make sure that the msvc toolset doesn't do
anything with <threading>single when the version is >= 8.
-- Dave Abrahams Boost Consulting www.boost-consulting.com