[Configure] gdFontCacheSetup requires gd 2.0.16

[jlacroix]

In bug 1223, a call to gdFontCacheSetup have been added. This Function seems to
be added only in GD 2.0.16
http://www.boutell.com/gd/manual2.0.16.html#whatsnew2.0.16

MapServer currently require GD 2.0.12.

We need to update the configure and help or to make the code accept 2.0.12.
Any opinion?

Sean, Is this function is really needed when not using thread?

[sgillies@…]

It is only needed for multi-threaded use.  This might mean mod_php, might not.
Definitely affects Java mapscript.

I'll make the changes so that gdFontCacheSetup is only included for GD 2.0.16+.

[sdlime]

For 4.5+ we might as well just require 2.0.16 and higher rather than introducing
unnecessary complexity into the build process and the code. I would pull the
modification from 4.4 then, if it was made there. My 2 cents...

Steve

[sgillies@…]

Let's try to resolve this one soon, yes?

[jlacroix]

After thinking about it for a bit, I agree with Steve. We may just require the
2.0.16 version for 4.5 if there's no other way to do it. However, we should not
require it for 4.4.

Sean, will you update the configure of 4.5? If not, please reassign the bug to
mapserver-bugs@dmsolutions dot ca. We will take care of it before 4.6.

[dmorissette]

Fixing this now.

[dmorissette]

Fixed.

1- Nothing to do for MapServer 4.4 since hte gdFontCacheSetup() call was never
added there.

2- I modified the configure script to require GD 2.0.16 (used to be 2.0.12).
Specifically, I replaced the test that was looking for gdImageSetAntiAliased
(2.0.12) by a test to look for gdFontCacheSetup (2.0.16) in configure.in.

This means that it won't be possible to build with older version of GD, but
forcing people to upgrade may just be a good thing anyway since GD 2.0.29
contains a fix for a security vulnerability.