[Freetype] FreeType 2.0 SNAFU

[Bob Friesenhahn]

I am helping to prepare a new ImageMagick release which depends on
FreeType 2.0.  At the very last moment (since the last beta), the
installation directory for the FreeType headers was changed to default
to "/usr/local/include/freetype2".  Of course the user could have set
the prefix to any locally-reasonable location so the headers could be
hidden anywhere in several terabyte of disk ...

By itself this is not a problem (typically headers are installed where
the compiler will find them), but unfortunately, the FreeType headers
are included like <freetype/fterrors.h> so the only way to make the
inclusion work is by adding -I/usr/local/include/freetype2 to
CPPFLAGS.  There are no existing Autoconf tests which are capable of
finding headers installed in this fashion.  The only solution seems to
be to require the user to tell configure at which random place they
have chosen to install the headers so that CPPFLAGS can be extended to
include that location.  It it quite likely that the typical user won't
know the answer to this question.

Maybe I am wrong and I am missing something obvious.  What am I
missing?

Bob
======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen