[Using V2] usage-requirements

From: by way of Jürgen Hunold (hunold+lists.Boost_at_[hidden])
Date: 2003-02-24 04:33:24

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi !

I'm having difficulties with "usage-requirements".
It seems this feature does not work as I expected it to ;-(((

Problem-Description: (Example attached.)
I have an external library libx:
- -libx--include-libx-<header>
|-src/Jamfile

The src/Jamfile specifies <include>../include for both requirements 
and usage-requirements. So I should be able to include all headers 
from libx by using <libx/header.h>

My programm is has several components.
One library should be liba.
In the top-level-Jamfile of "program" I specify use-project libx.
I thought that _all_ sublevel Jamfile use now the correct library 
include for libx. Well, waht happens is that bjam sets the 
library-path only for the main-program which explicitly links to it.

Can someone take a look at this ?

Start by cd bjam/program/main and run bjam --v2.
Both main.cpp and bjam/program/liba/test_a.cpp try to include
#include <libx/test_libx.h>
It works in main but not in liba.
Is this a bug, feature or am I misinterpreting the docs ?

One other problem is caused by the qt toolset. Both libx and program 
try to use the qt-toolset in their project-root.jam. This leads to
conflicts. You can reproduce this by removing the comment in
libx/project-root.jam. Then try to build program with program/Jamfile. 
This
is not urgent, because I don't plan to build any 3rd party
qt-enhancement libraries any time soon, but could be a showstopper
for someone else ;-)

Yours, 

Jürgen

- --
* Dipl.-Math. Jürgen Hunold ! Institut für Verkehrswesen,
Eisenbahnbau * voice: ++49 511 762-2529 ! und -betrieb,
Universität Hannover * fax : ++49 511 762-3001 ! Appelstrasse 9a,
D-30167 Hannover * hunold_at_[hidden] !
www.ive.uni-hannover.de

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+WebnljbJ/LLrxrYRAgLUAKDF4ed1kGOhAFNDBl3qWykaFLmgTgCfRW3/
Zsr9kxeF0BN63COJO75YhIg=
=75nh
-----END PGP SIGNATURE-----
 --Boundary-00=_kbeW+eRCZ4Qy6tG Content-Type: application/x-tgz;
name="bjam.tar.gz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bjam.tar.gz"

[Attachment content not displayed.] --Boundary-00=_kbeW+eRCZ4Qy6tG--