Re: [Freetype] What modules to use?

[David Turner]

Hello David,

David Piepgrass wrote:

> I can't find any documentation to tell me what each module is for.
>
> I would like to make a minimal build of freetype for use on a CE device.  Can 
> someone tell me how to make a build with support for TrueType font files and 
> antialiasing but nothing else?
>
>  
You'll need the following modules:

- sfnt_module_class    ( SFNT font file "container" support)
- tt_driver_class          ( TrueType handling )
- ft_smooth_renderer_class  ( Anti-aliased renderer )

for LCD-decimated display (à la ClearType), you'll need also:
- ft_smooth_renderer_lcd_renderer_class or  ( horizontal LCD-optimized 
rendering )
- ft_smooth_renderer_lcdv_renderer_class or both ( vertical 
LCD-optimized rendering )

> Beyond this, what do I need to add in order to support:
> - Hinting (AutoHinting, I guess, since I don't have one of those Apple licence 
> thingies)
>  
that would be "autohint_module_class"

> - OpenType (*.otf) fonts
>  
use "cff_driver_class", it's used to support both CFF and OpenType (when 
"sfnt_module_class" is also availble)

> - The caching subsystem, if it actually works (has anyone used it?)
>
>  
it works, but I dont guarantee that the API won't change in subtles ways 
though. Though it's not
"production" code, Mozilla is already using it in their current releases...

> Finally, I would like to expose the freetype API as exports in a (Windows CE) 
> DLL, because I want to call the FreeType functions from a .NET Framework 
> program.  Is there an easy way to do this?
>
>  
yes, all public API functions are declared and defined with the help of 
two macros: FT_EXPORT() and FT_EXPORT_DEF()
Look at the comment in <freetype/config/ftoption.h> about them for more 
details. You should probably redefine them here
to match your compiler's semantics. Beware that due to the way Windows 
DLL work, you should use distinct macro
definitions when building the library, or simply when linking to it 
(i.e. when your program #includes the FreeType API headers)

> Any help is appreciated, including a pointer to a list of module descriptions 
> if one exists.
>
>  
Have you seen docs/modules.txt ?

Hope this helps,

Regards,

- David Turner
- The FreeType Project  (www.freetype.org)

> _______________________________________________
> Freetype mailing list
> address@hidden
> http://www.freetype.org/mailman/listinfo/freetype
>
>