Re: [Freetype] Re: Summary of ANSI preprocessor trouble..

[Sven Neumann]

Hi,

David Turner <address@hidden> writes:

>   We are now faced with two choices:
> 
>     - in one hand, we simply go back to #include <freetype/...>
>       and install the files in ../include/freetype2/freetype
>       on Unix systems, using the "freetype-config" script
>       to determine the correct "-I" flags (and others..)
> 
> 
>     - on the other hand, we still support #include <ft2build.h>
>       with macros, but we define them _directly_, with a definition
>       that changes with the install, like:
> [...]
> 
>   I'd like your opinions on the subject. I'm personnaly getting
>   really tired of this whole affair, as minor as it may be, and
>   strongly favor the first solution. After all, it's simple,
>   it already works, and I'm sure that a few old Unix monkeys
>   can learn a few new tricks ;-)
> 
> Any comments, ??

I have never understood why you started to fiddle with the 
header files again because I was quite happy with the new 
include path (../include/freetype2/freetype) and the inclusion 
of the freetype-config script.


Salut, Sven