On Sun, 16 Apr 2000, Snail Talk wrote:
> path convention :), actually a bit more serious than
> that. include files should go in /usr/include
> /usr/local/include, it's always been teh convention, i
> don't think it would be very nice if we break it.
> besides, it's not just about cooker, others may be
> compiling their own apps and specifying the include in
> /usr/include
I am currently developing a Qt application, and I think you're a bit
confused about Unix include file practices. The include files should
only go in /usr/include if they're going to actually be put in there
(i.e. NOT in /usr/include/qt) or unless they're supposed to be #included
like this:
#include <qt/qwidget.h>
This is how things like <sys/types.h> works, you'll notice. But that's
NOT how Qt is supposed to work. The above line should be:
#include <qwidget.h>
Thus, IF Qt headers are to be put into /usr/include, they should be put
there, not in /usr/include/qt or /usr/include/qt2 or anything like that.
The problem with THAT is that it makes it impossible to support multiple
versions of Qt. If we want to support multiple versions of the library,
then we need to manually specify the include path with the -I flag, in
which case it doesn't really matter where the include files go, even
your suggestion would be fine, but let's not pretend we're observing some
Unix standard by following it -- in fact we're abusing it. If we are to
follow it, we should do like X11 does with it's include files and libs:
make a /usr/qt2/include, /usr/qt2/libs, etc. They should NOT go in
/usr/include, they don't go there any more than the stuff in
/usr/X11R6/include goes there, and it doesn't. Let's stick to Unix
standards and leave Qt OUT of /usr/include.
