[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [ft] Still no luck not including modules

From: Turner, David
Subject: RE: [ft] Still no luck not including modules
Date: Thu, 27 Oct 2005 14:27:10 +0200

> -----Message d'origine-----
> De : address@hidden
> [mailto:address@hidden la part de
> Hisashi T Fujinaka
> Envoyé : lundi 24 octobre 2005 19:31
> À : address@hidden
> Objet : [ft] Still no luck not including modules
> I'm still trying to figure out how to exclude modules from
> the libraries
> compiled by freetype. I tried directly editing
> include/freetype/config/ftmodule.h, but ftwinfnt.(lo|o) was still
> getting created and linked in. I can't see where in the makefiles that
> this would make a difference. I'm not that well versed in
> Makefiles, but
> they look fairly straightforward.
> Are the makefiles not the way to go? Are they neglected in favor of
> Jamfiles?
I'm _heavily_ using the Jamfiles myself, so I tend to update them before
the Makefiles.

> The only way I could get things to work the way I thought they should
> work is to delete the winfonts directory in src.
Or you can rename the '' files to something else, that should
be enough for the Make build system.

If you use the Jamfiles, you can define an environment variable that lists
all the components you want to compile, separated by spaces. Each component
is the name of a sub-directory under 'src', e.g.:

export FT2_COMPONENTS="base raster smooth sfnt truetype"

but you still need to manually update <freetype/config/ftmodule.h> to change
the list of modules statically linked to ftinit.c though.

At the moment, the configuration process doesn't allow you to make this step
automatic. This could be handy, but I can think of a portable way to do that
simply at the moment. Probably some Python script to come in the future if
this becomes really necessary.


- David Turner
- The FreeType Project  (

Information contained in this email message is confidential and may be 
privileged, and is intended only for use of the individual or entity named 
above. If the reader of this message is not the intended recipient, or the 
employee or agent responsible to deliver it to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please immediately notify the address@hidden and destroy the original 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]