[Top][All Lists]

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

Re: [ft-devel] last fixes for forthcoming release

From: mpsuzuki
Subject: Re: [ft-devel] last fixes for forthcoming release
Date: Mon, 27 Feb 2006 16:41:21 +0900

Excuse me, I was misunderstanding new modularized building system.

On Mon, 27 Feb 2006 13:28:57 +0900
address@hidden wrote:
>1. Makefile in ft2demos should refer freetype2/modules.cfg,
>   but does not at present. Therefore, is
>   built without gxvalid/otlavid module by default, but
>   make -C ft2demos tries to build ftvalid and failed.

In module.cfg, gxvalid, otvalid, ftgxval are disabled,
but ftotval is enabled. I think ftgxval and ftotval
are thin wrappers to provide public interface of gxvalid
and otvalid modules.

The interface functions in ftgxval and ftotval return
errors safely, when libfreetype is built without gxvalid
and otvalid. So, I think, ftgxval/ftotval should be
enabled always, except of the cases that the memory
filled by these wrappers are not negligible (e.g. very
small systems). If ftgxval/ftotval are always built,
we can always build ftvalid, and ft2demos/Makefile
is not needed to be modified.

But, now I found that modules.cfg disables ftgxval.
ft2demos/Makefile should be capable for such cases?


reply via email to

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