Re: [Freetype] FreeType 2.0 SNAFU

[Werner LEMBERG]

> Cpp-calculated include paths are not considered portable across all
> compilers.  This is even true for C++ compilers.

???  Please explain.

> Take care with file extensions since Windows likes to associate
> programs with extensions.  There is no telling what it does with
> extensions on directory names.

As said in another mail, my suggestion is now obsolete.

> It seems unfortunate to require the build environment to pass a -D
> option to allow the headers to work.  Other package's headers "just
> plain work".  Why can this not be true for FreeType as well?

No need to worry.  Wait a bit for the new code.


    Werner