On Tue, Jan 30, 2018 at 1:45 PM, Tom Kacvinsky <tkacv...@gmail.com> wrote: > Hi all, > > I'll see what I can do. To be honest, the only platforms that really > support this > are Linux and Solaris. I definitely have access to Linux machines, but not > a > Solaris machine. I might be able to get access to the latter.
virtualbox + openindiana ? Vincent Torri > Despite all of the talk about whether symbol versioning is useful (and this > is not > meant to be snarky), keep in mind the major commercial Linux distributions > use > symbol versioning, as well as the free Linux distributions. I work for SUSE > and > my colleagues highly recommend getting symbol versioning into FreeType. I > agree with them and am willing to do the work as I find time - as the > saying goes, > put my money where my mouth is. > > The only thing I would need is a way of getting the API functions to add to > a > symbol versioning linker file. This way, the symbol versioning script > doesn't > need to be checked in, and if we add something to the API, we don't need to > worry about missing it in the library version file. > > Regards, > > Tom > > On Tue, Jan 30, 2018 at 1:25 AM, Werner LEMBERG <w...@gnu.org> wrote: >> >> >> > Admittedly, symbol versioning is very poorly supported and >> > documented [...] >> >> Yes. >> >> > [...] All in all, this looks like something to stay away from. >> >> Maybe there are more knowledgeable people who want to contribute... >> >> >> Werner > > > > _______________________________________________ > Freetype-devel mailing list > Freetype-devel@nongnu.org > https://lists.nongnu.org/mailman/listinfo/freetype-devel > _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
