Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
> On 03/08/08 19:12, Clemens Kirchgatterer wrote:
> > Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
> >> I still believe, though, that freetype2's include files are broken.
> >> A simple '#include <freetype2.h>' should be enough. If their header
> >> file(s) would behave like the rest, we wouldn't have this
> >> discussion.
> > no. pkg-config and freetype-config have absolutly nothing to do with
> > that. i think nearly every "obtional" library has one of these to
> > provide a way to find them at compile and link time. please see the
> > output of: ls /usr/bin/*-config
> But would it kill anybody to simply have all header files at
> a standard place (/usr/include and /usr/local/include)?
yes it would. how would you install different versions of the same
libraries (with their headers) if it wasn't in different paths? and
what about cross compilers? the possibillity of having libs and headers
in different places is a very important feature, not an anoying bug.
> Why should every application go on a scavenger hunt to find
> all the header files it needs?
see above. anyway, thats the way it was since many many years for good
reasons. it's the standard way of finding compiler and linker flags
for libraries and you like obeying standards, don't you?
vdr mailing list