[xorg-bugzilla-noise] [Bug 556] RFE: Update FreeType2 version in xc/extras/Freetype2 to V2.1.8...

[bugzilla-daemon at pdx.freedesktop.org]

http://pdx.freedesktop.org/cgi-bin/bugzilla/show_bug.cgi?id=556





------- Additional Comments From eich at pdx.freedesktop.org  2004-05-06 18:59 -------
Roland Mainz wrote:

> I found the difference yesterday... my fault... but I was preparing a patch for
> the Freetype.org CVS to include that fix... is that no longer needed now ?

Right. It is only needed for the 'static' module build. But for this I've added
a define to myftstdlib.h. For any other case myftstdlib.h will include the
default ftstdlib.h which in turn includes limits.h.

> Erm... will that mean that I cannot build a Xserver with a statically linked
> Freetype module and Freetype library ? Remember that our own Xprint.org > releases
> always linked Freetype statically for stability and maintaince reasons... and it
> will take a couple of years until all distributions have adopted at least
> FreeType 2.1.8. Please do not do that...

That's what I would like to find out before I do the changes. In theory if you
link against a dynamic lib that is later than the one on the system and you
install this lib on your system later on the loader should pick this one over
the system provided one. However you do a 'static' Xprint server anyway so you
should be able to link against a static libfreetype2.a which could be the one
supplied by the freetype2 package as you don't need the ugly module stuff
anyway. I've heared people suggest that once freetype can deal with CID fonts
we should link the server against freetype and forget about all font render
modules anyway.
I don't know if this will happen as companies supplying commercial font
renderers may become pretty upset.
Besides I think as far as freetype versions and 'older systems' are concerned
X'whatever' and Xprint are in the same boat: fontconfig already depends on 
freetype 2.1.7. Only that the Xprint folks have been running into this problem
before as they had to deal with customers while everything else is still rather
experimental and has not hit the mainstream user yet.
Therefore I don't think you should be worried too much ;-)




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.