Re: [jamboost] Re: Including 3rd party libraries with optional location

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-12-24 07:08:32

Hi Jim,

> 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:
....
> -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.

I think your analysis is correct. I'll fix this for m11, but probably not 
right now.

- Volodya