Boost logo

Boost Testing :

From: John Maddock (john_at_[hidden])
Date: 2006-03-20 06:00:12

Robert Ramey wrote:
> I added -d2 to the bjam commmand line and here is what I got. (a small
> portion) - I certainly seems that the stl port directories are
> included first.
> I have the INCLUDE environmental variable set - I'm wondering if thats
> it. This is kind of frustrating was mscv 6.0 builds with stlport
> 4.3.3 so it seems it would be something with environmental variables or
> some
> such

Setting INCLUDE shouldn't be an issue: that's how I run tests as well, and
it works just fine for me:

$ bjam -a -d2 demo_pimpl.obj
...found 565 targets...
...updating 1 target...

    "cl" /Zm800 -nologo
/Zc:forScope -I"..\..\..\bin\boost\libs\serialization\example" -I"c:\da
ta\boost\develop\boost" -I"c:\download\open\stlport\STLport-5.0.0\stlport" -I"c:
\data\boost\develop\boost" -Fo"..\..\..\bin\boost\libs\serialization\example\de
pl.obj" -Tp"demo_pimpl.cpp"

Linking to lib file: libboost_serialization-vc71-mt-gdp-1_34.lib
Linking to lib file: libboost_serialization-vc71-mt-gdp-1_34.lib
...updated 1 target...

What the auto-link output is telling you in your case, is that STLport is
not in the include path - try going into libs/config/test then

bjam config_info

and then examine the output logged to the .out file in the
directory: the config_info output will tell you which std lib is in effect.

OK, really stupid question: your STLport really is in c:\STLport-5.0 is it?
I just don't see how it can fail at present if it is.


Boost-testing list run by mbergal at