On Tue, Apr 3, 2018 at 11:34 AM, Nikolaus Waxweiler <[email protected]> wrote:
> > (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? > I'd rather start with generic ftconfig.h, then generate ftconfig.in for autotools from it.
_______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
