Re: FreeType autoconf checks

[Alexandre Julliard]

Ian Pilcher  writes:
> One thing to keep in mind, however.  The FreeType headers themselves
> use relative paths to include one another, so this is an issue that
> we're not going to be able to completely eliminate.  This is why I
> had to mess around with the C_INCLUDE_PATH variable; AC_CHECK_HEADER
> tries to preprocess the header file, so it has to be able to find any
> subsidiary headers.  (Is this what you mean by finding a way to check
> that #include <freetype/freetype.h> works?)

Yes; we should be using only relative paths in AC_CHECK_HEADER, since
this is what we will use in the code. I don't think C_INCLUDE_PATH is
portable either. Did you try setting CPPFLAGS instead?

FreeType autoconf checks

[Ian Pilcher]

Alexandre Julliard wrote:
> Yes; we should be using only relative paths in AC_CHECK_HEADER, since
> this is what we will use in the code. I don't think C_INCLUDE_PATH is
> portable either. Did you try setting CPPFLAGS instead?

CPPFLAGS works.  Where the heck is that documented?  (I can't find it in
the info pages for gcc or cpp.)

Updated patch will follow.