> (1) without any build tools (e.g., flat-directory compilation, as discussed 
> in file `INSTALL.ANY');

So how would a universal ftconfig.h.in fit in here? If you generate
one for `make dist`, you're going to bake in platform specifics, no?

_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel

Reply via email to