[cp-patches] Re: Make qt-peers build and run out of the box

[Dalibor Topic]

Mark Wielaard wrote:
> Hi,
>
> If you think that is wrong maybe there is a bug in the .pc files?
> I looked but couldn't find any bug report against this.

I believe that is a bug in the pc files, that my sed appendix tries to 
work around. I'll report it upstream.

> I am not against using another convention then required by the
> pkg-config files.  But that feels wrong since it means we are trying to
> second guess the results of pkg-config which was supposed to make our
> lives easier. 

results of pkg-config made my life easier? Yeah, right ;) By having a 
CFLAGS setting for C++ source code, where automake expects them in 
CXXFLAGS? ;)

pkg-config is pretty useful for some C-based things, like GNOME. It is 
not very useful outside of them. In this case, pkg-config is useful to 
check that the version of Qt meets our requirements. That's cool.

Through a wink of chance, it also seems to provide useful linker flags, 
and *almost* useful compiler flags. I would not rely on pkg-config for 
that, since it is, for all I know about Qt, in general not used by 
anyone to write Qt applications, and Trolltech really only supports 
using qmake. Debian even forgot to ship the pc files for a while in 3.3 
series and hardly anyone noticed. ;)

> If someone could figure out why pkg-config gives us CFLAGS
> that seem unintuitive to some that would be appreciated.

Because the CFLAGS setting in the pc files in the lib/ directory in the 
qt 4.0.1 source code miss the respective module directory entries. They 
should be trivial to fix for 4.0.2, though.

cheers,
dalibor topic