Re: [jamboost] Need Help w/Prebuilt Targets and Include Path

From: Caleb Epstein (caleb.epstein_at_[hidden])
Date: 2004-12-09 11:53:15

On Thu, 9 Dec 2004 19:25:22 +0300, Vladimir Prus <ghost_at_[hidden]> wrote:

> Given Jamroot of:
> 
> lib tools : [ glob src/*.cpp ] log4cplus # tibrvcpp
> : <include>include ;
> 
> lib log4cplus : : <search>/path/to/log4cplus/lib : :
> <include>/path/to/log4cplus/include ;
> 
> I get:
> [...]
> So you have a testcase.

Actually I over-simplified my example. What I *really* have is:

lib libported : [ glob ported/src/BAS[A-CE-Z]*.cpp ] BASDiagnostics ;
obj BASDiagnostics : ported/src/BASDiagnostics.cpp log4cplus ;
lib log4cplus [ ... as before ... ]

The BASDiagnostics object file is the only one which requires
log4cplus, and it is built correctly. But when the library is built,
-llog4cplus is passed to the linker without any -L flags as I reported
previously. If I add log4cplus to the "lib libported" line, the
linking works as expected.

So basically <search> seems to be getting lost in this extra level of
indirection that I am doing.

> > 2. The current BBV2 doesn't seem to support versioned shared libraries
> > correctly. Taking a cue from example/versioned/jamfile.jam, I have:
> >
> > lib libported : [ glob ported/src/*.cpp ] : <version>1.0 ;
> >
> > But the linker is invoked with "-Wl,-h -Wl,libported.so" and not
> > "libported.so.1.0" which I would expect.
> 
> That example is out of date, I'm afraid. Try
> 
> stage dist : libported : <so-version>1.0 ;

OK this works, but I needed to pull the latest code from CVS. With
the 1.32.0 codebase, I get errors when I use <so-version>.

> In a recent email, I've asking options on whether <so-version> should be used
> on 'lib' targets. I'd appreciate if you read that email and comment. The
> subject is "RFC: naming, dll versions and installing".

I will read and respond on that topic.

> You can use
> 
> import os ;
> local OS = [ os.name ] ;

That'll do. Thanks.

-- 
Caleb Epstein
caleb dot epstein at gmail dot com