> Oh oh. Looks like the times of "easy building" of ttfautohint are
> gone :(
>
> It now requires a huge Qt library. I don't mind the ability to have
> a GUI tool but to require Qt in order to build a simple commandline
> app is somewhat of an overkill, especially if one wants to deploy
> the tool on a GUI-less server. I'd greatly appreciate an ability to
> build without the Qt dependancy.
Will do.
> Also the build process seems to have added complication. I used to
> be able to build ttfautohint on Mac OS X as either a 32-bit Intel or
> a 64-bit Intel commandline app. Now calling:
>
> $ ./configure --with-freetype-config=`pwd`/../out/bin/freetype-config
> --prefix=`pwd`/../out \
> CFLAGS="-Os -arch i386"
>
> no longer is sufficient because the Qt flags seem to insist on
> x86_64, and I don't yet know how to work around it.
This is something I have to ask on a Qt forum.
> But even if I decide to build x86_64, the new "bootstrap" stuff adds
> even more complication to the mix. I downloaded the most recent
> libtool and installed it (bootstrap insisted on it), and now
> bootstrap pulls some "gnulib" stuff, which then seems to conflict
> with the headers that come pre-installed on my Mac OS X. See below.
This shouldn't happen. Probably a bug. I'll report it to the gnulib
people.
Thanks for testing!
Werner
_______________________________________________
Freetype mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype
