Hi Werner and all,
Perhaps we shall *rename* the library to, say, `libft2', instead of
`libfreetype', together with a new API prefix `FT2_' instead of `FT_'.
This would avoid the whole mess.
Simply changing the library name is not going to change a lot of things
due to the way dynamic
Hello Drew,
thanks a *lot* for this e-mail. Here's what I've understood of the
situation:
- first of all, the fact that the code includes t42types.h means that the
original developer assumed that Xprint was using the version of FreeType
embedded within the X server, since this header has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Perhaps we shall *rename* the library to, say, `libft2', instead of
`libfreetype', together with a new API prefix `FT2_' instead of `FT_'.
This would avoid the whole mess.
Yeah, that and to keep binary compatibility a stub library could be
written
On Mon, 2006-01-23 at 01:53, david turner wrote:
Perhaps we shall *rename* the library to, say, `libft2', instead of
`libfreetype',
Um this will break everybody's builds and will mean we can't have
something that builds with either 1.10 or 2.0 without fancy configure
scripting. I'm not sure
