From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-01-29 01:21:01
Jürgen Hunold wrote:
> Am Dienstag 28 Januar 2003 17:08 schrieb Vladimir Prus:
>>I've just added the first version of stlport module for V2. I have
>>in examples-v2/hello. All works as expected. The second command line
>> uses stlport with native iostreams.
> Thanks, Vladimir. I've copied this and it basically works.
> Some flaws:
> Toolset does not specify Llibrary path with -L option. It therefore
> doesn't link on my machine because I'm not using vendor-stlport (SuSE)
> but own version patched for gcc-3.2.1 and my programs.
Oops, that's a documentation issue. You can say something like
using stlport : /usr/include/stlport : /opt/lib ;
to specify /opt/lib as location of stlport library. In general, if
using something ...
is given, you can look at rule "init" in something.jam to figure out what
configuration parameters can be passed.
> (Hardcoding dll-path with -Wl,-rpath would be great, too).
Would adding -Wl,-rpath *anywhere* in the command line help? I though that
no, in which case this feature cannot be implemented immediately.
> It does not work with qt-toolset. bjam says:
> hunold_at_stofi:~/develop/laden/gui> bjam --v2 stdlib=stlport
> /home/hunold/packages/boost/tools/build/new/feature.jam:777: in
> *** argument error
> * rule qt.qt.add-properties ( property )
> * called with: ( <uses>qt : <stdlib>stlport <os>LINUX <toolset>gcc
> <link>shared <link-runtime>shared <optimization>off <threading>single
> <rtti>on <debug-symbols>on <hardcode-dll-paths>true <variant>debug
> <include>. <include>/usr/local/STLport-4.5.3/stlport
> <include>/home/hunold/packages/boost <uses>qt )
[ snip ]
> I've skipped the rest of the messages since they do not seem to be
> The problem seems to be the "extra argument" line. I don't know what
> triggers this.
Oh, damn! I've changed some interface for the sake of stlport toolset, and
that broke qt. Really, plain regression tests are not enough -- have to
test examples too. Should be fixed now.
>>Support for debug mode is next thing --- once I figure out how to use
>>it by hand.
> Simplest use: specify _STLP_DEBUG and link against -lstlport_gcc_debug.
> This enables the debug engine. You can then specify more specific debug
> options (see stlport/stl_user_config.h)
Yea, that's what I though is right. Maybe it's just bad luck, but I get linker
errors, and if I add "-lpthread" I only reduce the number of them. Maybe some
configuration problem here.
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