Re: [ft] Freetype memory allocation

[Werner LEMBERG]

>> I cannnot move the flush of the drawing operations at the end of
>> the for loop for performances reason of my embedded application. Is
>> there a clean way to avoid the automatic memory deallocation in
>> freetype?

No.  You have to copy the bitmap, either by doing this manually or
using the glyph cache.

> I don't mean to suggest the caching interface is trivial to
> understand, but I recommend starting with the documentation if you
> want to use it:
> https://www.freetype.org/freetype2/docs/reference/ft2-cache_subsystem.html.

And please look up the FreeType demo programs for some example code.

> It seems like the FreeType caching mechanism does not support GPU
> acceleration which is probably one of the major reasons why people
> do not use it.

Patches and/or suggestions how FreeType could be improved are highly
welcomed :-)


    Werner