[Fontconfig] Build issue help needed...

Philip Schneider philip at pixologic.com
Tue Mar 19 17:13:35 PDT 2013

Yes, thanks…that makes more sense…got misled by some random internet post :-(

In any case, since this now-correct usage lets me see more what is going on: I now see that the need for the freetype and expat lib specifications is that the default compilation target includes the creation of a number of command-line programs, which utilize those libs (as well as libfontconfig, I suppose :-) )

So, with the clarification/correction you provided, I am able to cleanly compile the entire thing (just had to add "-lz" to the FREETYPE_LIBS macro)

Again, thanks!

- Philip

On Mar 18, 2013, at 11:08 PM, Akira TAGOH <akira at tagoh.org> wrote:

> On Sun, Mar 17, 2013 at 3:07 AM, Philip Schneider <philip at pixologic.com> wrote:
>> FREETYPE_CFLAGS="-I/MyStuff/dev/external/FreeType/freetype-2.4.8/include"
>> FREETYPE_LIBS=/MyStuff/dev/lib/Flash/build-flascc/lib/libfreetype.a
>> EXPAT_LIBS=/MyStuff/dev/lib/Flash/build-flascc/lib/libexpat.a
>> EXPAT_CFLAGS="-I/MyStuff/dev/external/expat/expat/expat/lib"
> Use them instead of above *_LIBS:
> FREETYPE_LIBS=-L/MyStuff/dev/lib/Flash/build-flascc/lib -lfreetype
> EXPAT_LIBS=-L/MyStuff/dev/lib/Flash/build-flascc/lib -lexpat
> That should works. please make sure you don't have shared libraries on
> the same place.
> -- 
> Akira TAGOH

More information about the Fontconfig mailing list