hi.
i recently played a bit with a G5 and tried to compile Gem on OS-X (10.4.7) via the autoconf system.
good news:
basically changing the line dealing with "-bundle" in configure(.ac) did the trick; it is already in the CVS (plus some minor changes, which should the use of configure a bit simpler; like "--with-pd" not pointing to the pd-executable anymore, but to the base path where both the pd-executable/library (./bin) and the headers (./src) can be found)
i only forgot about ftgl-support, which i did today, trying to make everything from the command-line (which might - or not - be important for the hans's autobuild system; basically i believe that freetype2 and ftgl should not be included in the nightly builds, as they are virtually never-changing; so they could be built via some IDE like xcode once and then the building of Gem would run without gui)
all in all, it was not hard to do, and here is how i did it:
### START
## i have ${GEMROOT}/Gem/src/ and ${GEMROOT}/GemLibs/ $> export GEMROOT=/Users/zmoelnig/src/pd-gem ## ${PDPATH}/src/m_pd.h $> export PDPATH=/Users/zmoelnig/src/pure-data/pd ## openGL-headers are in ${X11OPENGL}/GL/gl.h $> export X11OPENGL=/Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/
$> cd ${GEMROOT}/GemLibs
## freetype2
$> wget http://download.savannah.gnu.org/releases/freetype/freetype-2.2.1.tar.bz2 $> tar xvzf freetype-2.2.1.tar.bz2 $> cd ${GEMROOT}/freetype-2.2.1/ $> ./configure $> make ## this installs freetype2 into /usr/local/: $> sudo make install
## since FTGL's build system needs to run freetype-config, we ## need /usr/local/bin in our path $> export PATH=$PATH:/usr/local/bin
## FTGL
$> wget http://opengl.geek.nz/ftgl/ftgl-2.1.2.tar.gz $> tar xvzf ftgl-2.1.2.tar.gz $> cd ${GEMROOT}/FTGL/unix $> ./configure --with-ft-prefix=/usr/local/ --with-gl-inc=${X11OPENGL}/include/ --with-gl-lib=${X11OPENGL}/lib/ $> make
## allright, that's it; we don't have to do the above for months, ## probably years!
## here's how i compiled Gem with the above settings
$> export PKG_FTGL_CFLAGS="-I${GEMROOT}/GemLibs/FTGL/include/ $(freetype-config --cflags)" $> export PKG_FTGL_LIBS="$(freetype-config --libs) ${GEMLIBS}/GemLibs/FTGL/unix/src/.libs/libftgl.a" $> ./configure --with-pd=${PDPATH} $> make
### END
(actually i didn't use "export" for the PKG_FTGL_... vars, but set them in the same line as calling configure:
$> PKG_FTGL_CFLAGS="-I${GEMROOT}/GemLibs/FTGL/include/ $(freetype-config --cflags)" PKG_FTGL_LIBS="$(freetype-config --libs) ${GEMLIBS}/GemLibs/FTGL/unix/src/.libs/libftgl.a" ./configure --with-pd=${PDPATH}
i haven't yet spotted any problems with my built (but probably i have linked the freetype2-lib dynamically, which i guess i should NOT do. what is the standard tool on os-x to find out the dll-dependencies of a binary? something like "ldd" on linux.
mf.asdr. IOhannes
There are some issues with this.
- We don't use the X11 GL at all. It should be the OpenGL and AGL frameworks - FTGL should not use the X11 GL either - freetype and FTGL are linked statically
On 8/10/06, IOhannes m zmoelnig zmoelnig@iem.at wrote:
hi.
i recently played a bit with a G5 and tried to compile Gem on OS-X (10.4.7) via the autoconf system.
good news:
basically changing the line dealing with "-bundle" in configure(.ac) did the trick; it is already in the CVS (plus some minor changes, which should the use of configure a bit simpler; like "--with-pd" not pointing to the pd-executable anymore, but to the base path where both the pd-executable/library (./bin) and the headers (./src) can be found)
i only forgot about ftgl-support, which i did today, trying to make everything from the command-line (which might - or not - be important for the hans's autobuild system; basically i believe that freetype2 and ftgl should not be included in the nightly builds, as they are virtually never-changing; so they could be built via some IDE like xcode once and then the building of Gem would run without gui)
all in all, it was not hard to do, and here is how i did it:
### START
## i have ${GEMROOT}/Gem/src/ and ${GEMROOT}/GemLibs/ $> export GEMROOT=/Users/zmoelnig/src/pd-gem ## ${PDPATH}/src/m_pd.h $> export PDPATH=/Users/zmoelnig/src/pure-data/pd ## openGL-headers are in ${X11OPENGL}/GL/gl.h $> export X11OPENGL=/Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/
$> cd ${GEMROOT}/GemLibs
## freetype2
$> wget http://download.savannah.gnu.org/releases/freetype/freetype-2.2.1.tar.bz2 $> tar xvzf freetype-2.2.1.tar.bz2 $> cd ${GEMROOT}/freetype-2.2.1/ $> ./configure $> make ## this installs freetype2 into /usr/local/: $> sudo make install
## since FTGL's build system needs to run freetype-config, we ## need /usr/local/bin in our path $> export PATH=$PATH:/usr/local/bin
## FTGL
$> wget http://opengl.geek.nz/ftgl/ftgl-2.1.2.tar.gz $> tar xvzf ftgl-2.1.2.tar.gz $> cd ${GEMROOT}/FTGL/unix $> ./configure --with-ft-prefix=/usr/local/ --with-gl-inc=${X11OPENGL}/include/ --with-gl-lib=${X11OPENGL}/lib/ $> make
## allright, that's it; we don't have to do the above for months, ## probably years!
## here's how i compiled Gem with the above settings
$> export PKG_FTGL_CFLAGS="-I${GEMROOT}/GemLibs/FTGL/include/ $(freetype-config --cflags)" $> export PKG_FTGL_LIBS="$(freetype-config --libs) ${GEMLIBS}/GemLibs/FTGL/unix/src/.libs/libftgl.a" $> ./configure --with-pd=${PDPATH} $> make
### END
(actually i didn't use "export" for the PKG_FTGL_... vars, but set them in the same line as calling configure:
$> PKG_FTGL_CFLAGS="-I${GEMROOT}/GemLibs/FTGL/include/ $(freetype-config --cflags)" PKG_FTGL_LIBS="$(freetype-config --libs) ${GEMLIBS}/GemLibs/FTGL/unix/src/.libs/libftgl.a" ./configure --with-pd=${PDPATH}
i haven't yet spotted any problems with my built (but probably i have linked the freetype2-lib dynamically, which i guess i should NOT do. what is the standard tool on os-x to find out the dll-dependencies of a binary? something like "ldd" on linux.
mf.asdr. IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
On Aug 10, 2006, at 12:52 PM, chris clepper wrote:
There are some issues with this.
- We don't use the X11 GL at all. It should be the OpenGL and AGL
frameworks
- FTGL should not use the X11 GL either
- freetype and FTGL are linked statically
On 8/10/06, IOhannes m zmoelnig zmoelnig@iem.at wrote: hi.
i recently played a bit with a G5 and tried to compile Gem on OS-X (10.4.7) via the autoconf system.
good news:
basically changing the line dealing with "-bundle" in configure (.ac) did the trick; it is already in the CVS (plus some minor changes, which should the use of configure a bit simpler; like "--with-pd" not pointing to the pd-executable anymore, but to the base path where both the pd-executable/library (./bin) and the headers (./src) can be found)
i only forgot about ftgl-support, which i did today, trying to make everything from the command-line (which might - or not - be important for the hans's autobuild system; basically i believe that freetype2 and ftgl should not be included in the nightly builds, as they are virtually never-changing; so they could be built via some IDE like xcode once and then the building of Gem would run without gui)
With the auto-builds, it has to be in CVS or the OS's package system (Fink for OSX). It has to be this way, otherwise its far too much work to maintain. I think FTGL and freetype2 are in Debian, but they are not in Fink, and I don't know about Ubuntu, Fedora Core, or PlanetCCRMA.
Anything in CVS will be built from scratch every night. The source is rsync'ed against a clean copy every night, so all binaries are wiped clean.
For MinGW, they can be built from source outside of CVS since there is no other option, I am already maintaining a list of working sources. They will need to install with one or two commands, like "./ configure && make install" or just a "make install", otherwise they need to be in CVS.
.hc
all in all, it was not hard to do, and here is how i did it:
### START
## i have ${GEMROOT}/Gem/src/ and ${GEMROOT}/GemLibs/ $> export GEMROOT=/Users/zmoelnig/src/pd-gem ## ${PDPATH}/src/m_pd.h $> export PDPATH=/Users/zmoelnig/src/pure-data/pd ## openGL-headers are in ${X11OPENGL}/GL/gl.h $> export X11OPENGL=/Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/
$> cd ${GEMROOT}/GemLibs
## freetype2
$> wget http://download.savannah.gnu.org/releases/freetype/ freetype-2.2.1.tar.bz2 $> tar xvzf freetype-2.2.1.tar.bz2 $> cd ${GEMROOT}/freetype-2.2.1/ $> ./configure $> make ## this installs freetype2 into /usr/local/: $> sudo make install
## since FTGL's build system needs to run freetype-config, we ## need /usr/local/bin in our path $> export PATH=$PATH:/usr/local/bin
## FTGL
$> wget http://opengl.geek.nz/ftgl/ftgl-2.1.2.tar.gz $> tar xvzf ftgl-2.1.2.tar.gz $> cd ${GEMROOT}/FTGL/unix $> ./configure --with-ft-prefix=/usr/local/ --with-gl-inc=${X11OPENGL}/include/ --with-gl-lib=${X11OPENGL}/lib/ $> make
## allright, that's it; we don't have to do the above for months, ## probably years!
## here's how i compiled Gem with the above settings
$> export PKG_FTGL_CFLAGS="-I${GEMROOT}/GemLibs/FTGL/include/ $(freetype-config --cflags)" $> export PKG_FTGL_LIBS="$(freetype-config --libs) ${GEMLIBS}/GemLibs/FTGL/unix/src/.libs/libftgl.a" $> ./configure --with-pd=${PDPATH} $> make
### END
(actually i didn't use "export" for the PKG_FTGL_... vars, but set them in the same line as calling configure:
$> PKG_FTGL_CFLAGS="-I${GEMROOT}/GemLibs/FTGL/include/ $(freetype- config --cflags)" PKG_FTGL_LIBS="$(freetype-config --libs) ${GEMLIBS}/GemLibs/FTGL/unix/src/.libs/libftgl.a" ./configure --with-pd=${PDPATH}
i haven't yet spotted any problems with my built (but probably i have linked the freetype2-lib dynamically, which i guess i should NOT do. what is the standard tool on os-x to find out the dll-dependencies of a binary? something like "ldd" on linux.
mf.asdr. IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
chris clepper wrote:
There are some issues with this.
- We don't use the X11 GL at all. It should be the OpenGL and AGL
frameworks
- FTGL should not use the X11 GL either
that's actually just one point: i only used X11-GL for building FTGL; (that's a problem with FTGL's configure-script which is meant for "unix" but not really of "osX"; the script is looking for "GL/gl.h" and fails if it cannot find it)
Gem itself is built using the OpenGL/AGL frameworks.
- freetype and FTGL are linked statically
this is known (note that i only linked freetype dynamically, while i linked ftgl statically).
for better checking, i repeat my question: how do i check the dynamic linkage dependencies of a binary on osx?
i still think that it will be easiest to provide the binaries for freetype2 and ftgl in the GemLibs-OSX-10.4.tgz
nfga.dsr IOhannes
On Aug 11, 2006, at 5:16 AM, IOhannes m zmölnig wrote:
this is known (note that i only linked freetype dynamically, while i linked ftgl statically).
...freetype is available from fink:
freetype 1.3.1-9 TrueType font rendering library, version 1 freetype-bin 1.3.1-9 TrueType font rendering library, version 1 freetype-hin... 1.3.1-9 TrueType font rendering library, version 1, ... freetype-hin... 1.3.1-9 TrueType font rendering library, version 1, ... freetype-hin... 1.3.1-9 TrueType font rendering library, version 1, ... freetype-shlibs 1.3.1-9 TrueType font rendering library, version 1 freetype2 2.1.4-12 TrueType font rendering library, (dummy) i freetype2-dev 2.1.4-12 TrueType font rendering library, headers freetype2-hi... 2.1.4-12 TrueType font rendering library, (dummy) freetype2-hi... 2.1.4-12 TrueType font rendering library, headers freetype2-hi... 2.1.4-12 TrueType font rendering library, shared libs i freetype2-sh... 2.1.4-12 TrueType font rendering library, shared libs i freetype219 2.1.9-2 TrueType font rendering library, headers i freetype219-... 2.1.9-2 TrueType font rendering library, shared libs
...note that you always get shared libs, which means you would need to include it in the distribution, or explicitly specify linking to the static lib (which is usually also built)...I always do this in the ftgl archive, so that ftgl can be build statically, and therefore is portable (no probs so far)...
for better checking, i repeat my question: how do i check the dynamic linkage dependencies of a binary on osx?
otool -L name.dylib will show dependent libs, or "otool -L libftgl.a" will show object files included...
i still think that it will be easiest to provide the binaries for freetype2 and ftgl in the GemLibs-OSX-10.4.tgz
...I agree: we really just need a correctly built libftgl.a in GemLibs/libs...but I'm sick with some unknown (yet) swelling of the lymph nodes in my neck, and can't do much...
bleh, jamie
On Aug 11, 2006, at 2:56 PM, james tittle wrote:
On Aug 11, 2006, at 5:16 AM, IOhannes m zmölnig wrote:
this is known (note that i only linked freetype dynamically, while i linked ftgl statically).
...freetype is available from fink:
freetype 1.3.1-9 TrueType font rendering library,version 1 freetype-bin 1.3.1-9 TrueType font rendering library, version 1 freetype-hin... 1.3.1-9 TrueType font rendering library, version 1, ... freetype-hin... 1.3.1-9 TrueType font rendering library, version 1, ... freetype-hin... 1.3.1-9 TrueType font rendering library, version 1, ... freetype-shlibs 1.3.1-9 TrueType font rendering library, version 1 freetype2 2.1.4-12 TrueType font rendering library, (dummy) i freetype2-dev 2.1.4-12 TrueType font rendering library, headers freetype2-hi... 2.1.4-12 TrueType font rendering library, (dummy) freetype2-hi... 2.1.4-12 TrueType font rendering library, headers freetype2-hi... 2.1.4-12 TrueType font rendering library, shared libs i freetype2-sh... 2.1.4-12 TrueType font rendering library, shared libs i freetype219 2.1.9-2 TrueType font rendering library, headers i freetype219-... 2.1.9-2 TrueType font rendering library, shared libs
...note that you always get shared libs, which means you would need to include it in the distribution, or explicitly specify linking to the static lib (which is usually also built)...I always do this in the ftgl archive, so that ftgl can be build statically, and therefore is portable (no probs so far)...
for better checking, i repeat my question: how do i check the dynamic linkage dependencies of a binary on osx?
otool -L name.dylib will show dependent libs, or "otool -L libftgl.a" will show object files included...
That's already handled by the Pd-extended build system. Once the build is done, it automatically finds all the needed dylibs and includes them from Fink.
i still think that it will be easiest to provide the binaries for freetype2 and ftgl in the GemLibs-OSX-10.4.tgz
...I agree: we really just need a correctly built libftgl.a in GemLibs/libs...but I'm
Like I said before, checking in binaries is a really bad idea. If the code is "done", it should be simple to automate the building. This will lead to less work in the long run.
sick with some unknown (yet) swelling of the lymph nodes in my neck, and can't do much...
Get well soon!
.hc
Hans-Christoph Steiner wrote:
On Aug 11, 2006, at 2:56 PM, james tittle wrote:
for better checking, i repeat my question: how do i check the dynamic linkage dependencies of a binary on osx?
otool -L name.dylib will show dependent libs, or "otool -L libftgl.a" will show object files included...
thanks jamie
That's already handled by the Pd-extended build system. Once the build is done, it automatically finds all the needed dylibs and includes them from Fink.
the answer to my question is not handled by pd-extended. i was simply interested in how to obtain this dylib information on os-x (totally unrelated to pd)
i still think that it will be easiest to provide the binaries for freetype2 and ftgl in the GemLibs-OSX-10.4.tgz
...I agree: we really just need a correctly built libftgl.a in GemLibs/libs...but I'm
Like I said before, checking in binaries is a really bad idea. If the
i was not talking about putting these into CVS but as a "dependencies package" downloadable from the homepage.
code is "done", it should be simple to automate the building. This will lead to less work in the long run.
volunteers?
sick with some unknown (yet) swelling of the lymph nodes in my neck, and can't do much...
Get well soon!
best wishes from here too...
mfg.sa IOhannes
On Aug 11, 2006, at 7:19 PM, IOhannes m zmölnig wrote:
Hans-Christoph Steiner wrote:
On Aug 11, 2006, at 2:56 PM, james tittle wrote:
for better checking, i repeat my question: how do i check the dynamic linkage dependencies of a binary on osx?
otool -L name.dylib will show dependent libs, or "otool -L libftgl.a" will show object files included...
thanks jamie
That's already handled by the Pd-extended build system. Once the build is done, it automatically finds all the needed dylibs and includes them from Fink.
the answer to my question is not handled by pd-extended. i was simply interested in how to obtain this dylib information on os-x (totally unrelated to pd)
Sorry, I am tired, I misread...
The big advantage of Fink is that the dependencies are automatically included. Also, right now the only Pd-extended dependency not in Fink is Jack. I just noticed that Jack is now in Fink, so the Framework can be replaced.
Of course, y'all can handle this however you want, but for the compile farm, Fink and compiling out of CVS are the only supported method of installing deps.
.hc
i still think that it will be easiest to provide the binaries for freetype2 and ftgl in the GemLibs-OSX-10.4.tgz
...I agree: we really just need a correctly built libftgl.a in GemLibs/libs...but I'm
Like I said before, checking in binaries is a really bad idea. If the
i was not talking about putting these into CVS but as a "dependencies package" downloadable from the homepage.
code is "done", it should be simple to automate the building. This will lead to less work in the long run.
volunteers?
sick with some unknown (yet) swelling of the lymph nodes in my neck, and can't do much...
Get well soon!
best wishes from here too...
mfg.sa IOhannes
Hans-Christoph Steiner wrote:
the answer to my question is not handled by pd-extended. i was simply interested in how to obtain this dylib information on os-x (totally unrelated to pd)
Sorry, I am tired, I misread...
nevermind
Of course, y'all can handle this however you want, but for the compile farm, Fink and compiling out of CVS are the only supported method of installing deps.
OK. in this case, the os-x autobuilds will be without FTGL support until ftgl gets included into fink (i really don't have a problem with this)
mfg,ads IOhannes
Meaning pd-extended will only have gltt support rather than ftgl?
I propose the following:
* FTGL is included in gemlibs (GemLibs/FTGL)
with some small changes to the provided xcode project: * Make paths relative to where the Xcode project is for src,include * Assume the freetype2 lib is provided by fink and lives in /sw/lib/freetype2/
I can build the FTGL static lib with:
cd FTGL/mac xcodebuild
which puts ftgl.a in FTGL/mac/build/
Assuming this will be in GemLibs/FTGL/mac/build how can we get the configure script to find it?
Looks like I'm not a gem developer so I can't check in.
Can someone put FTGL in GemLibs and replace the FTGL.xcode with the one attached?
At least there is a step...
Thanks, .b.
IOhannes m zmölnig wrote:
Hans-Christoph Steiner wrote:
the answer to my question is not handled by pd-extended. i was simply interested in how to obtain this dylib information on os-x (totally unrelated to pd)
Sorry, I am tired, I misread...
nevermind
Of course, y'all can handle this however you want, but for the compile farm, Fink and compiling out of CVS are the only supported method of installing deps.
OK. in this case, the os-x autobuilds will be without FTGL support until ftgl gets included into fink (i really don't have a problem with this)
mfg,ads IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Looks like no one has responded to this.
What's the problem with this approach?
Of course FTGL could be in GemLibs/darwinStuff/FTGL if that is better for ya'll....
Thanks, .b.
B. Bogart wrote:
Meaning pd-extended will only have gltt support rather than ftgl?
I propose the following:
- FTGL is included in gemlibs (GemLibs/FTGL)
with some small changes to the provided xcode project:
- Make paths relative to where the Xcode project is for src,include
- Assume the freetype2 lib is provided by fink and lives in
/sw/lib/freetype2/
I can build the FTGL static lib with:
cd FTGL/mac xcodebuild
which puts ftgl.a in FTGL/mac/build/
Assuming this will be in GemLibs/FTGL/mac/build how can we get the configure script to find it?
Looks like I'm not a gem developer so I can't check in.
Can someone put FTGL in GemLibs and replace the FTGL.xcode with the one attached?
At least there is a step...
Thanks, .b.
IOhannes m zmölnig wrote:
Hans-Christoph Steiner wrote:
the answer to my question is not handled by pd-extended. i was simply interested in how to obtain this dylib information on os-x (totally unrelated to pd)
Sorry, I am tired, I misread...
nevermind
Of course, y'all can handle this however you want, but for the compile farm, Fink and compiling out of CVS are the only supported method of installing deps.
OK. in this case, the os-x autobuilds will be without FTGL support until ftgl gets included into fink (i really don't have a problem with this)
mfg,ads IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
I am assuming that FTGL is also used on Windows. If its going to be included in CVS, it would make a lot of send to put it in a place where the Windows build system can get to it too.
.hc
On Aug 25, 2006, at 3:22 PM, B. Bogart wrote:
Looks like no one has responded to this.
What's the problem with this approach?
Of course FTGL could be in GemLibs/darwinStuff/FTGL if that is better for ya'll....
Thanks, .b.
B. Bogart wrote:
Meaning pd-extended will only have gltt support rather than ftgl?
I propose the following:
- FTGL is included in gemlibs (GemLibs/FTGL)
with some small changes to the provided xcode project:
- Make paths relative to where the Xcode project is for src,include
- Assume the freetype2 lib is provided by fink and lives in
/sw/lib/freetype2/
I can build the FTGL static lib with:
cd FTGL/mac xcodebuild
which puts ftgl.a in FTGL/mac/build/
Assuming this will be in GemLibs/FTGL/mac/build how can we get the configure script to find it?
Looks like I'm not a gem developer so I can't check in.
Can someone put FTGL in GemLibs and replace the FTGL.xcode with the one attached?
At least there is a step...
Thanks, .b.
IOhannes m zmölnig wrote:
Hans-Christoph Steiner wrote:
the answer to my question is not handled by pd-extended. i was simply interested in how to obtain this dylib information on os-x (totally unrelated to pd)
Sorry, I am tired, I misread...
nevermind
Of course, y'all can handle this however you want, but for the compile farm, Fink and compiling out of CVS are the only supported method of installing deps.
OK. in this case, the os-x autobuilds will be without FTGL support until ftgl gets included into fink (i really don't have a problem with this)
mfg,ads IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
-
B. Bogart -
chris clepper -
Hans-Christoph Steiner -
IOhannes m zmoelnig -
IOhannes m zmölnig
-
james tittle