Thats cool, I think thats an elegant solution. Then I dont get why I still get this message from Gem:
[text2d]: Gem has been compiled without FONT-support !
This is from the latest auto-build (may 9). I can clearly see the libfreetype.6.dylib in the correct path.
Well I'm still very green at this, hope you can figure it out. I will keep testing the nightly-builds for font
support. This process has been my first experience with compiling anything. BTW i was able to get
text support going by including the static library within the Gem build. Gem blew up to 4.2MB, its a
fatty but it works for my purposes.
Alain
From: Hans-Christoph Steiner hans@eds.org Date: 2007/05/09 Wed AM 12:49:15 EDT To: Nose Hair nosehair911@bellsouth.net CC: gem-dev@iem.at, Pure Data List pd-list@iem.at Subject: Re: [GEM-dev] [PD] Gem Compiling os x xcode problems
Actually, using Fink, I have scripted the build system to
automatically include any dynamic libs that are needed. This is
already working well for ogg, vorbis, speex, and now PDP stuff. I
see no reason why it shouldn't work for Gem too.If you look in Pd.app/Contents/lib you can see all the included .dylibs.
.hc
On May 8, 2007, at 10:24 PM, Nose Hair wrote:
I tested last nights auto-build and it still says gem is compiled
without font support. I will give tonight's build a shot and let
you know. BTW I think that a static lib pointing to the X11
freetype is the way to go because if someone already has x11
installed they don't have to compile and install freetype from
scratch. It's not hard but it would be more of a pain as opposed
to installing the X11 package from their Tiger DVD. AlainOn May 8, 2007, at 9:00 PM, Hans-Christoph Steiner wrote:
Does freetype have to be statically linked? Will it work with
dynamic? Right now, the auto-build compiles with a dynamic
freetype lib, and I have a script that includes all the required
dynamic libs..hc
On May 8, 2007, at 10:26 AM, chris clepper wrote:
Use static linking for freetype and FTGL on OSX.
On 5/8/07, nosehair911@bellsouth.net < nosehair911@bellsouth.net>
wrote: I have gotten Gem to compile sucesfully with font support using
the xcode project somewhat. I get 1125 warnings, mainly this is the location of the previous
definition. My biggets problem is that in my machine I have the latest freetype under usr/local/lib and I also have
the freetype that comes with x11 under usr/ X11R6/lib. When I load gen in my machine it loads up fine with
text support, but when I load up gem in a machine with only the freetype in usr/X11R6/lib Gem will not load
up because it keeps looking for the libfreetype.6.dylib in usr/local/lib. I dont know how to remedy
this. Any help would be great. Thanks, Alain
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
All information should be free. - the hacker ethic
¡El pueblo unido jamás será vencido!
nosehair911@bellsouth.net wrote:
Thats cool, I think thats an elegant solution. Then I dont get why I still get this message from Gem:
[text2d]: Gem has been compiled without FONT-support !
This is from the latest auto-build (may 9).
which autobuild? currently there are several versions of pd-extended built each night, probably one of them uses the old non-font Gem?
Well I'm still very green at this, hope you can figure it out. I will keep testing the nightly-builds for font support. This process has been my first experience with compiling anything. BTW i was able to get text support going by including the static library within the Gem build. Gem blew up to 4.2MB, its a fatty but it works for my purposes.
well, that's the joy auf static linking (and that is one of the reasons why on w32 and os-x most apps are so huge, while on linux most of them are tiny)
mfg.adr IOhannes
-
IOhannes m zmoelnig -
nosehair911＠bellsouth.net