|
Boost-Build : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-09-11 03:56:22
On Tuesday 11 September 2007 08:57:58 Modwel, Manoj wrote:
>
> Hello,
>
> Thank you so much for your reply.
> This cxxflags=-I$STLPORT_INCLUDE} is a typo (it actually is
> cxxflags=-I${STLPORT_INCLUDE}
>
> Ok, I have changed my script and now I am running bjam this way:
>
> bjam --builddir=${TEMP_BUILD} --prefix=${PREFIX} variant=release
> threading=multi link=shared stdlib=stlport \
> toolset=gcc --libdir=${BOOST_LIB} --includedir=${PREFIX}/include install
> --debug-configuration --debug-building --debug-generators -d+2
>
> The 'using' directive, in user-config.jam file is as:
> using gcc : : : <cxxflags>-m64 <address-model>$(ARCH)
> <architecture>native <cxxflags>-m$(ARCH) <linkflags>-m$(ARCH)
> <linkflags>-lstlport_gcc ;
> using stlport : 5.1.3 :
> /home/qt/build/jdep/20070730/Linux-x86_64-64/include/stlport-5.1.3/stlpo
> rt /home/qt/build/jdep/20070730/Linux-x86_64-64/lib/stlport-5.1.3 ;
>
> In the dry run (calling bjam with -o), I noticed that the the library
> name for stlport is '-lstlport.5.1' (wondering where the bjam is taking
> that?).
Can you be more specific? What's wrong with that library name? It would be
more helpful if you include the entire compile line that you find wrong.
> Also, I noticed that if I removed 'stdlib=stlport' from bjam command
> line (the using stlport is still as it is), include path does not
> includes stlport headers.
Yes, that's right and as designed. You should specify stdlib=stlport if you
want to use stlport.
- Volodya
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