Sven Johannsen wrote:
Hi,
when you compile the current boost with the following cmd-line the thread-lib has a wrong filename:
bjam "-sTOOLS=msvc-stlport" "-sSTLPORT_PATH=D:\Develop" "-sSTLPORT_VERSION=4.5.3"
this cmd-should generate "gdpn" files like: boost_thread-vc6-mt-gdpn-1_31.dll
but it generate a "gdp" (without "n") file. the "n" stands for native iostreams. (boost_thread-vc6-mt-gdp-1_31.lib)
That's because building with <stlport-iostreams>on is the default.
the lib behave like "gdpn"-file, but i have to rename the lib. otherwise i get the following linker error:
LINK : fatal error LNK1104: cannot open file "boost_thread-vc6-mt-gdpn-1_31.lib"
I think this is because the defines that the autolink is using don't match what the msvc-stlport-toolset.jam is setting.
who can modifier the jam-file. (i don't speak jam)
Try using the attached mscv-stlport-tools.jam see if things improve. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq # The following #// line will be used by the regression test table generation # program as the column heading for HTML tables. Must not include version number. #//<a href="http://msdn.microsoft.com/vstudio/default.asp">Micro-<br>soft<br>VC++</a><br><a href="http://www.stlport.org/">STLport</a> { # This is simply an extension to the msvc toolset. However, # STLPort doesn't have any single-threaded builds, so we're going # to force all such targets to be built with multithread support. # This is essentially a usage-requirement on the stlport library. local gBUILD_PROPERTIES = [ difference $(gBUILD_PROPERTIES) : <threading>single ] <threading>multi ; extends-toolset msvc ; } CURR_TOOLSET = msvc-stlport ; STLPORT_LIB_BASE_NAME = stlport_vc6 ; # bring in the STLPort configuration SEARCH on stlport.jam = $(BOOST_BUILD_PATH) ; include stlport.jam ;