Re: [jamboost] [BBv2] qt.jam glitches

From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-09-18 04:01:46

Hi Jürgen,

> I'm just trying to get my programs to be built with msvc-7.1.
> I've encountered several problems with qt.jam.

[snip]

Thanks for reporting those. I'll look at them in more detail a little bit 
later, but I've an interesting remark to make....

> Third, generated include paths.
> This is a real show stopper. I tried to compile RailSys with msvc and it
> stops due to command line overflow. This is due to the fact that the
> generated include paths of some 30 libraries appear on the commandline
> for the main() routine and bjam (cl.exe) chokes on this...

You might not believe, but this issue is already in my optimization todo for 
M8. Not only that, it's right at the top of priority queue.

> What I need is the following: Each library/exe should only its use its
> own generated includes.
> And I need to explicitly include generated include path from child and
> sister-projects. Without this feature, my test case would not work,
> because I have to add generated include path for lib/gui to app in
> order to #include "hello_world_widget.h" in main.cpp.

What a coincidence! Unless I've misunderstood you, you proposing just what I 
meant to implement.

1. Automatic dependency on generated headers works only within one main 
target.
2. It should be possible to explicitly specify other main target, if using 
headers from it, like

exe main : main.cpp : <implicit-dependency>cpp_parse ;

Is that what you propose, too?

- Volodya