Re: gnuplot with libgd for Windows?

[Ethan M. <merritt@u.washington.edu>]

On Tuesday 06 April 2004 10:24 am, you wrote:
> On Tue, 6 Apr 2004, Ethan Merritt wrote:
> > These minimal built-in fonts are provided as fall-backs in the case
> > that better ones are not provided by the operating environment.
>
> You need more than just the fonts --- you still need the freetype
> library to access them, too, I think.

Yes, that's probably true.

> So it seems we could withdraw to a position stated in INSTALL that says:
>
> gnuplot+Windows+(current GD built as DLL)+(no libfreetype) == NO GO

But even if freetype is present, we would still need conditional code in
gd.trm so that it doesn't generate unresolved symbol errors at build time,
right?
And also to make sure the default font was set to something reasonable.

> AFAICS, this problem will not happen as soon as one of these conditions
> is removed.  Having libfreetype around or just using a statically
> compiled GD would probably be the easiest alternatives.

Is it easy to build libgd as static under windows?  If that's a way out of the
bind let's do that.  INSTALL can simply say (leaving open the possibility
that dlls will work again in the future):  "If you get unresolved symbol errors
for the fonts, please link against a static libgd library instead of the dll".
Or whatever the proper wording is for windows linkage.


-- 
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center
Mailstop 357742
University of Washington, Seattle, WA 98195