Yo,
> > /usr/include
>
> I am currently developing a Qt application, and I think you're a bit
> confused about Unix include file practices. The
no i'm not :) i'll explain.
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:
yeh i know, i look at C code myself, but it wold be quite funny when you
find include files in /usr/lib, they don't erally belong there either that's
why i asked for a symlink from whereever qt2's installed to point to
/usr/include/qt2 for the header files. don't forget that i'm aware of some
application spec pointing to /usr/include/qt2 for qt headers.
the case is a little awkward with qt since ti's not really anything but a
library, the executable files are probably only the moc file.
oh and BTW, i'm not sure where the moc is now, but will probably be better
in /usr/bin. the old 2.0.x had it called /usr/bin/moc2, to prevent trouble
with the moc from qt 1.x again if moc needs to be in libs for QTDIR to work,
then teh symlink from QTDIR --> /usr/bin/moc2 would be a godo idea.
> 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,
it should not be a problem since we have qt and qt2 as separte dir in the
include dir.
> 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
using the -I/usr/include/qt2 is ok, it's not too troublesome.
but you just do it in configure ...unless you don't have a configure script
;)
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
the case with qt is a little awkward since X11R6 is the whole XFree System
while for qt it is just a bunch of libraries. so teh libraries should
probably go in /usr/libs/qt-$VERSION (with symlinks in /usr/lib, perhaps)
but that will leave the header files with no place to belong to. you have to
choose the lesser of the two evils here, which would be /usr/include/qt2
_not_ /usr/libs/qt-$VERSION it's not a matter of where they belong now, it's
just where they belong better. i think include would be better than libs.
again, i've already asked for a compromise to point from QTDIR -->
/usr/include/qt2.
> /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.
>
