svn trunk error

[Steve Lime]

Do we dare require folks to hack other libs build assets? I'm worried about turning folks
off of the AGG support simply because it's so friggin' hard to get freetype working. Could
we detect freetype support in AGG and enable it in MapServer, otherwise fall back to the
GD font rendering? It's not a terrible alternative and better than 100's of emails to MapServer
users.

Steve

>>> On 8/7/2007 at 11:03 AM, in message <46B897C3.2060908 at pobox.com>, Frank
Warmerdam <warmerdam at POBOX.COM> wrote:
> Kralidis,Tom [Burlington] wrote:
>>  
>> I added -laggfontfreetype to AGG_LIB (thanks Thomas!) in Makefile and
>> everything built fine.  Apparently Frank is working on this one.
> 
> Tom,
> 
> I have updated mapserver to include -laggfreetype in the link.  But
> this means that folks building agg themselves from source will be
> obligated to create a libaggfreetype.a in their agg-2.4/src directory.
> 
> I *think* adding the following target to agg-2.4/src/Makefile, and then
> invoking "make libs" should do the trick.
> 
> libs:	all ../font_freetype/agg_font_freetype.o
> 	$(LIB) libaggfreetype.a ../font_freetype/agg_font_freetype.o
> 
> Ah yes, you also still need to add `freetype-config --cflags` or equivelent
> in CXXFLAGS.
> 
> Best regards,