> For libraries in LSB we generally avoid importing things like
> 'config.h' since they tend to define macros that are of interest
> when building the library but not of direct relevance to the API or
> ABI.
>
> Are there any cases where (say macros), depend on the defines in
> ftconfig.h?
You mean include/freetype/config/ftconfig.h, right? This file is only
needed if you compile FreeType without a configure script. The latter
is in builds/unix (after executing the autogen.sh script in case you
are using a CVS version of FreeType) which uses
builds/unix/ftconfig.in to create a platform specific version of
ftconfig.h.
> fttypes.h seems to nicely encapsulate the API/ABI types independantly
> from ftconfig.h. Bad/Good assumption?
What do you mean with `independently'?
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
