Re: [jamboost] [Qt-Toolset] bug in path resolution

From: David Abrahams (dave_at_[hidden])
Date: 2003-01-23 11:28:02

Vladimir Prus <ghost_at_[hidden]> writes:

> Jürgen Hunold wrote:
>> Hi !
>> 
>> First of all, I want to thank Vladimir for the great work.
>> I've tried the qt-toolset on some small project and it works fine.
>> 
>> Vladimir, the description for external Libraries was very helpful.
>> I was able to link against external libraries succesfully. All that 
>> prevents me from *really' using bjam is the following bug:
>
> [...]
>
> Jürgen,
>
> first off, thanks for providing such a good bug report. I'll respond in
> as much detail as I can, but note that the last paragraph of this email
> are enough to solve the issue.
>
> The problem can be explained by the following output from
> bjam --v2 --debug-generators
>
> *** construct LIB
> from { test_a.CPP }
> from { ../include/test_a.H }
> properties: [snip]
>
> # here we're trying to build liba/liba
>
> Later on:
> *** construct OBJ (may return multiple targets)
> from { ../include/test_a.H }
> properties: [snip]
> [snip]
> FAILURE
>
> The build system was unable to convert "H" source to anything. The reason
> is simple: moccing is allowed *only* if you have <uses>qt in properties and
> there's no that property when creating liba/liba.
>
> This can be easily fixed: Just add <uses>qt to "requirements" section of
> top-level Jamfile.

This is weird, because when I tried to test it, I removed all
qt-related stuff from Jürgen's project and still got the same
problem. Are you sure there isn't something else going on?

-- 
David Abrahams
dave_at_[hidden] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution