Re: Including 3rd party libraries with optional location

From: jim_at_[hidden]
Date: 2004-12-20 17:16:38

Vladimir Prus <jamboost_at_[hidden]> wrote:
>The code looks fine to me. I'll see why nothing is built on Monday.

I have a small self-contained illustration. In the distributed qt example,
just shift the 'import toolset/toolset.using qt' lines into the Jamfile,
thus:

--- Jamfile.orig	2004-12-20 22:09:56.000000000 +0000
+++ Jamfile	2004-12-20 22:10:01.000000000 +0000
@@ -3,6 +3,9 @@
# (See accompanying file LICENSE_1_0.txt
# or copy at http://www.boost.org/LICENSE_1_0.txt)

+import toolset ;
+toolset.using qt ;
+
project
# built MT version, unless asked otherwise.
: default-build <threading>multi 
--- project-root.jam.orig	2004-12-20 22:07:59.000000000 +0000
+++ project-root.jam	2004-12-20 22:08:04.000000000 +0000
@@ -1,9 +1,9 @@

-import toolset ;
+#import toolset ;

# Tell that QT should be used. QTDIR will give installation
# prefix. 
-toolset.using qt ;
+#toolset.using qt ;

#Alternatively, the prefix can be given as second argument
#toolset.using qt : /usr/share/qt ;

This doesn't seem an unreasonable thing to want to do, to localise external
requirements in the sub-component that requires them. But nothing will now
get built on m10, and CVS seems to suffer from the same project.

After some scattergun printfs, it looks to me like the reason is that the
Jamfile exe target is being added to the 'qt' project rather than the
Jamfile project. I presume somehow project.current is picking up qt.
-- 
Jim Hague - jim_at_[hidden] Never trust a computer you can't lift.