I'm all for incorporating agg_font_freetype.cpp and .h int the mapserver source tree and adding agg_font_freetype.o to the OBJS... we can always find a better solution when/if the antigrain guys change their builds<br>
tb<br><br><div><span class="gmail_quote">On 8/7/07, <b class="gmail_sendername">Steve Lime</b> <<a href="mailto:Steve.Lime@dnr.state.mn.us">Steve.Lime@dnr.state.mn.us</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Do we dare require folks to hack other libs build assets? I'm worried about turning folks<br>off of the AGG support simply because it's so friggin' hard to get freetype working. Could<br>we detect freetype support in AGG and enable it in MapServer, otherwise fall back to the
<br>GD font rendering? It's not a terrible alternative and better than 100's of emails to MapServer<br>users.<br><br>Steve<br><br>>>> On 8/7/2007 at 11:03 AM, in message <<a href="mailto:46B897C3.2060908@pobox.com">
46B897C3.2060908@pobox.com</a>>, Frank<br>Warmerdam <<a href="mailto:warmerdam@POBOX.COM">warmerdam@POBOX.COM</a>> wrote:<br>> Kralidis,Tom [Burlington] wrote:<br>>><br>>> I added -laggfontfreetype to AGG_LIB (thanks Thomas!) in Makefile and
<br>>> everything built fine. Apparently Frank is working on this one.<br>><br>> Tom,<br>><br>> I have updated mapserver to include -laggfreetype in the link. But<br>> this means that folks building agg themselves from source will be
<br>> obligated to create a libaggfreetype.a in their agg-2.4/src directory.<br>><br>> I *think* adding the following target to agg-2.4/src/Makefile, and then<br>> invoking "make libs" should do the trick.
<br>><br>> libs: all ../font_freetype/agg_font_freetype.o<br>> $(LIB) libaggfreetype.a ../font_freetype/agg_font_freetype.o<br>><br>> Ah yes, you also still need to add `freetype-config --cflags` or equivelent
<br>> in CXXFLAGS.<br>><br>> Best regards,<br></blockquote></div><br>