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 what it gains you that changing the so number doesn't...
> together with a new API prefix `FT2_' instead of `FT_'. > > This would avoid the whole mess. Please don't change the API. It makes some sense to change internal names, I suppose. I'd prefer you didn't (since fontforge is a rogue), but don't change the external ones. > Another option is to have ./configure refuse to install freetype 2.2.0 > if a previous release of the library is > detected on the system; that is, unless you use a super-duper parameter > like --please-destroy-my-desktop > that only the cautious will care to use. That seems like a good starting point to me. _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
