[Kde-games-devel] Forwarding includes for libkdegames

[Olivier Goffart]

Le samedi 30 décembre 2006 15:46, Matt Williams a écrit :
> Thinking about this some more; In Qt, to include, say, QApplication you do
> 	#include <QApplication>
> but not
> 	#include <Qt/QApplication>

That depends of the compilation options.  if the includes directory contains 
$QTDIR/include/QtGui or not

And because we want make possible to compile a kde program without that, 
kdelibs headers must contains the longner form
#include <QtGui/QApplication> 

> So why, in KDE, do we have it set up so that you need <KDE/KApplication>.
> There's no other file called KApplication so there should be no ambiguity
> and so a simple
> 	#include <KApplication>
> should suffice.

It suffice if you have $KDEDIR/include/KDE in your include path.

> So basically, is there any reason why the KDE forwarding headers were
> installed in the include/KDE directory and not just into /include?

- To do like Qt.
- to not fill /usr/include with tons of includes.

But I guess that now you know that KDE does the same as Qt, you're opinion has 
changed :-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20061230/b71f574e/attachment.sig>