Boost logo

Boost-Build :

From: Daniel Lidström (daniel.lidstrom_at_[hidden])
Date: 2006-10-11 04:59:47


Rene Rivera scribbled:

> You need to repeat the stlport init for each different version you
> compile and specify those versions when building. For example I have:
>
> using gcc : 3.4.5 : C:/MinGW/bin/g++.exe ;
> using stlport : 5.0~gcc345 :
> C:/DevRoots/STLport/STLport-5.0/stlport
> C:/DevRoots/STLport/STLport-5.0/lib
> C:/DevRoots/STLport/STLport-5.0/bin ;
> using stlport : 5.1~gcc345 :
> C:/DevRoots/STLport/STLport-5.1/stlport
> C:/DevRoots/STLport/STLport-5.1/lib
> C:/DevRoots/STLport/STLport-5.1/bin ;
>
> And you can then:
>
> bjam ... gcc/stdlib=stlport-5.1~gcc345
>
> It's also possible to specify the stlport build to use in the
> Jamfiles. And hence base it on the toolset automatically. For example
> by adding "<toolset>gcc-3.4.5:<stdlib>stlport-5.1~gcc345".

Thanks for the quick answer yesterday, Rene! I stumbled into some problems
linking with stlport.
This is working fine:

user-config.jam:

using stlport : :
      ../../Vendor/STLport/stlport
      ../../Vendor/STLport/lib
      ../../Vendor/STLport/bin ;

Jamroot:

      <toolset>msvc-6.0:<stdlib>stlport

But, if I try this (which should be the same):

using stlport : 5.0~msvc60 :
      ../../Vendor/STLport/stlport
      ../../Vendor/STLport/lib
      ../../Vendor/STLport/bin ;

      <toolset>msvc-6.0:<stdlib>stlport-5.0~msvc60

my target won't link with stlport:

bjam -q msvc-6.0
...
msvc.link.dll
bin\msvc-6.0\debug\stdlib-stlport-5.0~msvc60\stdlib-stlport-5.0~msvc60\GFL.d
ll
bin\msvc-6.0\debug\stdlib-stlport-5.0~msvc60\stdlib-stlport-5.0~msvc60\GFL.l
ib
LINK : fatal error LNK1181: cannot open input file "stlportstld.5.lib"

Indeed, there is no stlportstld.5.lib in STLport/lib. What is going on?
Thanks in advance!

Hälsningar,
Daniel
SBG AB

Phone: +4687112090
Fax : +4687112098
Location:
       59 14'10" N
       18 00'09" E


Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk