On Wed, 15 Nov 2000, Thomas Ribbrock wrote:
> Ok, maybe I'm confused, but how does that work if you want to compile
> other apps from tarball? $KDEDIR/include/kde is a non-standard location
> and even the header files themselves expect the stuff to be in
> $KDEDIR/include (example: kapps.h has a #include <kurl.h> ).
That's why they're using -I/usr/include/kde in the CFLAGS.
/usr/include/kde *is* one of the standard locations that gets searched
because it's the FHS compliant location.
$KDEDIR/include/kde won't work unless $KDEDIR == /usr.
What you can do is add --with-kde-includes=$KDEDIR/include/kde to the
configure parameters; most KDE applications will know what to do with
that.
LLaP
bero
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
