[mapserver-users] GD/Freetype Problem (was: No Image Output)

[Alexander Pucher]

Daniel,

sorry, but no, my build does _not_ work, unless I comment the 'Label'  
sections in the Gmap map file or I uncheck the 'Pop.Places' layer, which 
uses TTF!!!

Some more general questions, before I start it all over again on a clean 
system. I work on my private notebook, so setting up the whole thing 
again is no big deal!

Does 'SUPPORTS=TTF' in the 'mapserv -v' output:

MapServer version 3.6.1 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP 
SUPPORTS=PROJ SUPPORTS=TTF SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT 
INPUT=TIFF INPUT=EPPL7 INPUT=JPEG INPUT=POSTGIS INPUT=OGR INPUT=GDAL 
INPUT=SHAPEFILE

of my CGI mean that my mapserver executable supports Freetype 1? As I 
understood, TTF refers to  Freetype1 whereas FT ~ Freetype2 in all 
Makefiles etc. of the GD, PHP and Mapserver builds and configures. Is 
that correct? Does otherwise Freetype2 support show up with something 
like 'SUPPORT=FT' or 'SUPPORT=FREETYPE' ?

Can anyone on the list report on a successful build of mapserver 3.6.1 
on SuSE 8.0 with any GD/Freetype support?

What about using GD 2 or the newest mapserver nighly built. Should this 
change things?

Regards,
alex



Daniel Morissette wrote:

>Alexander Pucher wrote:
>  
>
>...
>  
>
>>checking for gdImageStringFT in -lgd... yes
>>checking for gdImageString16 in -lgd... yes
>>checking for gdImageGifPtr in -lgd... yes
>>        using GD ( -DUSE_GD_GIF -DUSE_GD_PNG -DUSE_GD_JPEG -DUSE_GD_WBMP
>>-DUSE_GD_FT -DGD_HAS_GDIMAGEGIFPTR) from system libs.
>>checking whether we should include PDF support...
>>...
>>
>>According to the MapServer Unix HOWTO, I should not get DUSE_GD_FT but
>>DUSE_GD_TTF, when building with Freetype1 !!!
>>
>>    
>>
>
>
>Hummm... you're correct that we would expect to see -DUSE_GD_TTF for
>freetype 1.3, that's odd... I checked on one of our servers and I get
>the same -DUSE_GD_FT as you with freetype1.3 and my truetype fonts work
>well, so I would suggest that you continue with your build... it's
>probably going to work.
>
>  
>