Boost logo

Boost-Build :

From: Modwel, Manoj (Manoj.Modwel_at_[hidden])
Date: 2007-09-11 04:24:29


Again many thanks for your reply.

Actually, there is nothing wrong with boost build system. Due to some
"internal" reasons we changed the default build names of STLPort library
and hence the linker fails when it is not able to find
(The default Stlport lib name).

I will appreciate if you could tell me is there any way to introduce
some tweak in any jam filr (stlport.jam ?) so that the stlport library
name should be what I want to (my changed name is
nstead of what boost build system picks (as, if not
probably a softlink is the only solution.

Best Regards,

-----Original Message-----
From: boost-build-bounces_at_[hidden]
[mailto:boost-build-bounces_at_[hidden]] On Behalf Of Vladimir Prus
Sent: Tuesday, September 11, 2007 4:56 PM
To: boost-build_at_[hidden]
Subject: Re: [Boost-build] Issues for building Boost 1.34.1

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
> --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 :
> 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
> that?).

Can you be more specific? What's wrong with that library name? It would
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
want to use stlport.

- Volodya
Unsubscribe & other changes:

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at