Re: [Boost-testing] [autolinking with stlport]

From: Robert Ramey (ramey_at_[hidden])
Date: 2006-03-20 01:16:00

I added th -d2 switch and ran bjam.  Here is what I got.  It sure looks to 
me
that the include path specifies the stlport directories.

Robert Ramey

MkDir1 
..\..\..\bin\boost\libs\serialization\test\test_polymorphic_text_archive.
test\vc-7_1-stlport

    mkdir 
"..\..\..\bin\boost\libs\serialization\test\test_polymorphic_text_arc
hive.test\vc-7_1-stlport"

MkDir1 
..\..\..\bin\boost\libs\serialization\test\test_polymorphic_text_archive.
test\vc-7_1-stlport\debug

    mkdir 
"..\..\..\bin\boost\libs\serialization\test\test_polymorphic_text_arc
hive.test\vc-7_1-stlport\debug"

MkDir1 
..\..\..\bin\boost\libs\serialization\test\test_polymorphic_text_archive.
test\vc-7_1-stlport\debug\threading-multi

    mkdir 
"..\..\..\bin\boost\libs\serialization\test\test_polymorphic_text_arc
hive.test\vc-7_1-stlport\debug\threading-multi"

vc-C++ 
..\..\..\bin\boost\libs\serialization\test\test_polymorphic_text_archive.
test\vc-7_1-stlport\debug\threading-multi\test_polymorphic.obj

    "cl"  /Zm800 -nologo 
EHsc -c  -DBOOST_ARCHIVE_TEST=polymorphic_text_archive
.hpp -DBOOST_LIB_DIAGNOSTIC=1 -D_STLP_DEBUG=1 -D_STLP_DEBUG_UNINITIALIZED=1  
-D_S
TLP_USE_DYNAMIC_LIB=1  /Z7 /Od /Ob0 /EHsc /GR /MDd /Op  -Gy /wd4675 
/Zc:forScope
  -I"..\..\..\bin\boost\libs\serialization\test"  -I"c:\STLport-5.0\stlport" 
  -I
"C:\BoostHead"   -Fo"..\..\..\bin\boost\libs\serialization\test\test_polymorphic
_text_archive.test\vc-7_1-stlport\debug\threading-multi\test_polymorphic.obj" 
  -
Tp"test_polymorphic.cpp"

test_polymorphic.cpp
Linking to lib file: libboost_serialization-vc71-mt-gd-1_34.lib
Linking to lib file: libboost_serialization-vc71-mt-gd-1_34.libJohn Maddock 
wrote:
>> and compiles everything - but the test programs fail to link with the
>> message
>>
>> LINK : fatal error LNK1104: cannot open file
>> 'libboost_serialization-vc71-mt-gd-1_34.lib'
>>
>> while I expect it to searchor
>> 'libboost_serialization-vc71-mt-gdp-1_34.lib
>> What am I missing here?
>
> The most likely explanation is that you are not in fact getting
> STLport injected into your compilers include path, so the auto-link
> code think's it's really seeing a vanilla MSVC install.  Try building
> with the -d2 switch so you can see the actual command lines.
>
> John.