Re: [jamboost] QT support, and some problems

From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-01-21 08:19:48

Felix E. Klee wrote:
> On Tuesday 21 January 2003 08:26, Vladimir Prus wrote:
> 
>>>OK, I attached a simple "Hello World!" project including the project file
>>>for qmake and the resulting Makefile.
>>
>>Initially I expected no problems at all, but then realized that H file
>>produced by UIC needs to be mocced. But that turned out to be only slightly
>>harder. Please go to examples-v2/qt-ui, run "bjam" and report your
>>experience.
> 
> 
> 1st try:
> [...]/examples-v2/qt-ui> bjam
> ...found 28 targets...
> ...updating 7 targets...
> qt.uic-h bin/gcc/debug/main-target-hello/hello_world_widget.h
> /bin/sh: hello_world_widget.ui: command not found
> 
> hello_world_widget.ui -o 
> bin/gcc/debug/main-target-hello/hello_world_widget.h 

I see the problem now. The reason is that Dave has fix a bug in Jam recently,
and I have not updated qt.jam: in contained a workaround for it. Please try 
again, with up-to-date bjam and Boost.Build.

> BTW, once you have that fixed, could you please make the extension of the 
> files generated by the uic customizable? I really prefer "h" to "hpp" and 
> some people might prefer eg. "cc" to "cpp".

I've no problem changing suffix for headers that UIC generates. In fact, it's
specified on line 36 of qt.jam. However, I'm not sure what our policy should
be. Do we allow to customize all extensions? Or would it be better to say that
UIC generates *target* types CPP and H and use default extension for that 
type. Or, should be allow the user to say: when generating headers, prefer the 
"hpp" extension.

- Volodya