> > So, we've had a report that building Ghostscript against Freetype > > 2.10.3 fails because FT_CALLBACK_DEF() has been moved to internal > > use only. > > > > Ghostcript supplies callbacks for memory management > > (i.e. FT_MemoryRec) and we used FT_CALLBACK_DEF() for those, which > > seemed logical when defining callbacks! > > Looks like an oversight to make it internal. Fact is that this macro > is not publicly documented... >
The internal description suggests that this is a placeholder for __attribute__((fastcall)) and __atribute__((cdecl)), which we do not use ourselves. > Is there now an alternative way to do that? Or should we just > > switch to explicitly declaring them static? Would ghostscript like to use those attributes?
