[Boost-build] bjam and moved shared libraries

From: Holger Bast (HolgerBast_at_[hidden])
Date: 2007-07-18 08:39:57

Hi Boost-Community,

I'm using bjam for a project at my university.
We had to build an application framework with bjam.

<root>
  <lib1>
  <lib2>
  <lib3>
  <tool1>
  <tool2>
  <tool3>

It works already, but there is an problem:
When I build the libs and the tools, bjam build them for example in
<root>
  <lib1>
    <bin>
      <gcc>
        <debug>

and my tools in

<root>
  <bin>
    <gcc>
      <debug>

I can start the tools without any problem. But I had to move the executables an the libraries to other directories.
So I created a "project" in my Jamroot and compiled them via "install"

here my Jamroot:

project test2007
        : build-dir ../build
        ;

using gcc ;

install ../lib
        :
        timer/final//timer
        stateframework//statef
        tracinglogging//tracelog
        :
        <install-dependencies>on
        <install-type>LIB
        ;

install ../bin
        :
        timer/final//timerserver
        uppertester//uppertester
        lowertester//lowertester
        datalinklayer//datalinklayer
        :
        <install-dependencies>on
        <install-type>EXE
        ;

install ../inc
        : [ glob tracinglogging/Interface/*.h ]
          [ glob stateframework/src/*.h ]
          [ glob timer/final/interface/*.h ]
          [ glob messagequeue/src/*.h ]
          [ glob messagequeue/src/*.cpp ]
        ;

And here a example of a library-Jamfile:

lib tracelog
        : [ glob ./src/Interface/*.cpp ]
        ;

I specified the problem, but I don't know how to solve it. The problem is, that the executables are searching the libs in folder, where bjam built them. But they were moved, because of "install".

I hope that anyone can help me.
Holger Bast