Hi, I posted a question last week on why [textextruded] wasnt
working. I got the answer, GEM must be compiled with FTGL.
So why was it changed in the first place? It seemed to be running
fine (or sort of) and now it aint working at all. And sadly I dont
know how to compile GEM with FTGL.
Whats the reason for this grand change? Any future benefits? Will it
support a full UTF-8 character map?
Sorry for complaining, Id so love to try the latest releases, but are
stuck with one from 10 months ago...
Cheers, T.
........................................................................ BotezCo Co/Timon Botez ........................................................................ www.botezco.com +44 (0) 798 998 5052
GEM moved to FTGL years ago. This was not a recent change at all.
On 4/19/07, timon timon@botezco.com wrote:
Hi, I posted a question last week on why [textextruded] wasnt working. I got the answer, GEM must be compiled with FTGL.So why was it changed in the first place? It seemed to be running fine (or sort of) and now it aint working at all. And sadly I dont know how to compile GEM with FTGL.
Whats the reason for this grand change? Any future benefits? Will it support a full UTF-8 character map?
Sorry for complaining, Id so love to try the latest releases, but are stuck with one from 10 months ago...
Cheers, T.
........................................................................
BotezCo
Co/Timon Botez
........................................................................
www.botezco.com
+44 (0) 798 998 5052
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
timon wrote:
Hi, I posted a question last week on why [textextruded] wasnt working. I got the answer, GEM must be compiled with FTGL. So why was it changed in the first place? It seemed to be running fine (or sort of) and now it aint working at all. And sadly I dont know how to compile GEM with FTGL.
please note that [textextruded] was only introduced into Gem because of FTGL (the old fontrendering library used was GLTT which had no such thing as extruded text).
so the answer is: in order to have [textextruded] working, you must compile Gem with FTGL; there have never been another way to get extruded text.
Whats the reason for this grand change? Any future benefits? Will it support a full UTF-8 character map?
like chris has said, there has not been a grand change regarding fonts for years. and yes, the text-objects in current CVS support full Unicode (well not full: only the first 65000 or so) characters.
mfga-sdr IOhannes
Hi, I posted a question last week on why [textextruded] wasnt
working. I got the answer, GEM must be compiled with FTGL. So why was it changed in the first place? It seemed to be running
fine (or sort of) and now it aint working at all. And sadly I dont know
how to compile GEM with FTGL.please note that [textextruded] was only introduced into Gem
because of FTGL (the old fontrendering library used was GLTT which had no such thing as extruded text).so the answer is: in order to have [textextruded] working, you must compile Gem with FTGL; there have never been another way to get
extruded text.
The versions I have been using has all that working. And from what
your saying, this version was compiled with FTGL.:
GEM: ver: 0.90
GEM: compiled: Mar 8 2006
This one is not: GEM: Graphics Environment for Multimedia GEM: ver: 0.91-cvs GEM: compiled: Apr 14 2007
So what your saying is that the current version of GEM is not
compiled with FTGL. I guess what Im trying to get an answer to is why
the current version of GEM is not compiled with FTGL? Are there any
plans for doing that (very impatient I know)?
Whats the reason for this grand change? Any future benefits? Will it support a full UTF-8 character map?
like chris has said, there has not been a grand change regarding fonts for years. and yes, the text-objects in current CVS support full Unicode (well
not full: only the first 65000 or so) characters.
With regards to full character set... I did some tests a while back,
with the older version (see above) which I posted on the list
(without much interest). The character mapping then was a bit messed
up. Importing UTF 8 format into PD is fine, but spitting it out to
any text object in GEM gets the characters jumbled up (the ones
outside the first 128). Also, it was not happy doing japanese, which
showed up fine in the symbol atom box. The only format it mapped
correctly was Windows Latin 1252 (all 256 characters - not really the
extended set I was hoping for). I did extensive tests on re-
formatting the fonts as well. Again, this came out with the same
result - correct for 1252 only. Beats me. Could this be an OS issue?
Im on OSX - whatever latest update.
T.
mfga-sdr IOhannes
timon wrote:
Hi, I posted a question last week on why [textextruded] wasnt working. I got the answer, GEM must be compiled with FTGL. So why was it changed in the first place? It seemed to be running fine (or sort of) and now it aint working at all. And sadly I dont know how to compile GEM with FTGL.
please note that [textextruded] was only introduced into Gem because of FTGL (the old fontrendering library used was GLTT which had no such thing as extruded text).
so the answer is: in order to have [textextruded] working, you must compile Gem with FTGL; there have never been another way to get extruded text.
The versions I have been using has all that working. And from what your saying, this version was compiled with FTGL.: GEM: ver: 0.90 GEM: compiled: Mar 8 2006
correct
This one is not: GEM: Graphics Environment for Multimedia GEM: ver: 0.91-cvs GEM: compiled: Apr 14 2007
So what your saying is that the current version of GEM is not compiled with FTGL. I guess what Im trying to get an answer to is why the current
correct
version of GEM is not compiled with FTGL? Are there any plans for doing that (very impatient I know)?
well of course; Gem's font support is designed to be compiled with FTGL on all platforms (btw, this was another bonus of using FTGL as it runs on linux, os-x and w32)
i don't know why your version of Gem is not compiled with FTGL, but i doubt that i compiled it (so i am not to blame).
if it is the version taken from pd-extended, than there is a reason for not having FTGL (well, even if it is not from pd-extended, i guess there is a reason for being compiled without FTGL; but in pd-extended i happen to know about it): compiling Gem with FTGL requires FTGL to be available on the compiling machine. this is simply not the case on the pd-extended OS-X build-machine, because there are no FTGL-packages available from fink. while the (deprecated) GemLibs do have a version of FTGL checked in, no automated build-system is provided for it. so FTGL gets not compiled on the build-system, which means that it is not available for Gem.
there are several things you can do about this:
step-by-step instructions how i did it in the gem-dev archives)
buil-machine and make Gem use it
Whats the reason for this grand change? Any future benefits? Will it support a full UTF-8 character map?
like chris has said, there has not been a grand change regarding fonts for years. and yes, the text-objects in current CVS support full Unicode (well not full: only the first 65000 or so) characters.
With regards to full character set... I did some tests a while back,
a "while back" is probably out of date. i have (hopefully) fixed this within the last 2 weeks. i have only tested it on linux, so i would be glad for w32 and os-x reports.
mfasdr IOhannes
Yes Im using the PD extended. Its a shame that this is changed. Sure
there will be others with similar questions.
Be happy to load an external version. Is there a compiled version for
OSX somewhere accessible? Had a look on the site and there are no
links anywhere...
Thanks for the feedback.
Best, T.
On 19 Apr 2007, at 15:33, IOhannes m zmoelnig wrote:
timon wrote:
Hi, I posted a question last week on why [textextruded] wasnt
working. I got the answer, GEM must be compiled with FTGL. So why was it changed in the first place? It seemed to be
running fine (or sort of) and now it aint working at all. And sadly I dont
know how to compile GEM with FTGL.please note that [textextruded] was only introduced into Gem
because of FTGL (the old fontrendering library used was GLTT which had no such thing as extruded text).so the answer is: in order to have [textextruded] working, you must compile Gem with FTGL; there have never been another way to get
extruded text.The versions I have been using has all that working. And from what
your saying, this version was compiled with FTGL.: GEM: ver: 0.90 GEM: compiled: Mar 8 2006correct
This one is not: GEM: Graphics Environment for Multimedia GEM: ver: 0.91-cvs GEM: compiled: Apr 14 2007
So what your saying is that the current version of GEM is not
compiled with FTGL. I guess what Im trying to get an answer to is why the
currentcorrect
version of GEM is not compiled with FTGL? Are there any plans for
doing that (very impatient I know)?well of course; Gem's font support is designed to be compiled with
FTGL on all platforms (btw, this was another bonus of using FTGL as it runs on linux, os-x and w32)i don't know why your version of Gem is not compiled with FTGL, but i doubt that i compiled it (so i am not to blame).
if it is the version taken from pd-extended, than there is a reason
for not having FTGL (well, even if it is not from pd-extended, i guess
there is a reason for being compiled without FTGL; but in pd-extended i
happen to know about it): compiling Gem with FTGL requires FTGL to be available on the compiling machine. this is simply not the case on the pd-extended OS-X build-machine, because there are no FTGL-packages available from fink. while the (deprecated) GemLibs do have a version of FTGL checked
in, no automated build-system is provided for it. so FTGL gets not compiled on the build-system, which means that it is not available for Gem.there are several things you can do about this:
- build Gem by hand (it is not that hard to do; you can find
step-by-step instructions how i did it in the gem-dev archives)
- try to get FTGL in GemLibs to be automatically build on the
buil-machine and make Gem use it
- try to get FTGL into fink
Whats the reason for this grand change? Any future benefits?
Will it support a full UTF-8 character map?like chris has said, there has not been a grand change regarding
fonts for years. and yes, the text-objects in current CVS support full Unicode
(well not full: only the first 65000 or so) characters.With regards to full character set... I did some tests a while back,
a "while back" is probably out of date. i have (hopefully) fixed this within the last 2 weeks. i have only tested it on linux, so i would be glad for w32 and os-x
reports.mfasdr IOhannes
On Thu, 2007-04-19 at 16:04 +0100, timon wrote:
Be happy to load an external version. Is there a compiled version for
OSX somewhere accessible?
http://gem.iem.at/download.html
Had a look on the site and there are no
links anywhere...
which site are you referring?
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
On 19 Apr 2007, at 20:18, Roman Haefeli wrote:
On Thu, 2007-04-19 at 16:04 +0100, timon wrote:
Be happy to load an external version. Is there a compiled version for OSX somewhere accessible?
http://gem.iem.at/download.html
Had a look on the site and there are no links anywhere...
which site are you referring?
roman
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http:// messenger.yahoo.de
On Apr 19, 2007, at 10:33 AM, IOhannes m zmoelnig wrote:
timon wrote:
Hi, I posted a question last week on why [textextruded] wasnt
working. I got the answer, GEM must be compiled with FTGL. So why was it changed in the first place? It seemed to be
running fine (or sort of) and now it aint working at all. And sadly I dont
know how to compile GEM with FTGL.please note that [textextruded] was only introduced into Gem
because of FTGL (the old fontrendering library used was GLTT which had no such thing as extruded text).so the answer is: in order to have [textextruded] working, you must compile Gem with FTGL; there have never been another way to get
extruded text.The versions I have been using has all that working. And from what
your saying, this version was compiled with FTGL.: GEM: ver: 0.90 GEM: compiled: Mar 8 2006correct
This one is not: GEM: Graphics Environment for Multimedia GEM: ver: 0.91-cvs GEM: compiled: Apr 14 2007
So what your saying is that the current version of GEM is not
compiled with FTGL. I guess what Im trying to get an answer to is why the
currentcorrect
version of GEM is not compiled with FTGL? Are there any plans for
doing that (very impatient I know)?well of course; Gem's font support is designed to be compiled with
FTGL on all platforms (btw, this was another bonus of using FTGL as it runs on linux, os-x and w32)i don't know why your version of Gem is not compiled with FTGL, but i doubt that i compiled it (so i am not to blame).
if it is the version taken from pd-extended, than there is a reason
for not having FTGL (well, even if it is not from pd-extended, i guess
there is a reason for being compiled without FTGL; but in pd-extended i
happen to know about it): compiling Gem with FTGL requires FTGL to be available on the compiling machine. this is simply not the case on the pd-extended OS-X build-machine, because there are no FTGL-packages available from fink. while the (deprecated) GemLibs do have a version of FTGL checked
in, no automated build-system is provided for it. so FTGL gets not compiled on the build-system, which means that it is not available for Gem.there are several things you can do about this:
- build Gem by hand (it is not that hard to do; you can find
step-by-step instructions how i did it in the gem-dev archives)
- try to get FTGL in GemLibs to be automatically build on the
buil-machine and make Gem use it
- try to get FTGL into fink
If I get FTGL in GemLibs building with the autobuilds, will you guys
keep FTGL there and accept my changes?
The amount of time we've spent discussing why this hasn't happened is
probably more time than it'll take to get just do it.
.hc
Whats the reason for this grand change? Any future benefits?
Will it support a full UTF-8 character map?like chris has said, there has not been a grand change regarding
fonts for years. and yes, the text-objects in current CVS support full Unicode
(well not full: only the first 65000 or so) characters.With regards to full character set... I did some tests a while back,
a "while back" is probably out of date. i have (hopefully) fixed this within the last 2 weeks. i have only tested it on linux, so i would be glad for w32 and os-x
reports.mfasdr IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
Computer science is no more related to the computer than astronomy is
related to the telescope. -Edsger Dykstra
So the first results are not so promising. It didn't build on either
Debian/stable or Mac OS X. Can anyone give me some of the hidden
secrets to building FTGL?
hans@sla:mac > xcodebuild
(NOTE: project FTGL was written by an older version of Xcode (39) --
temporarily upgrading it to version 42 (without modifying project file))
=== BUILDING NATIVE TARGET ftgl WITH THE DEFAULT CONFIGURATION
(Default) ===
Checking Dependencies...
CompileC build/FTGL.build/Default/ftgl.build/Objects-normal/ppc/
FTBitmapGlyph.o /Users/henry/Development/PROJECTS/FTGL/src/
FTBitmapGlyph.cpp normal ppc c++ com.apple.compilers.gcc.4_0
cd /Users/hans/code/pure-data/GemLibs/FTGL/mac
/usr/bin/gcc-4.0 -x c++ -arch ppc -pipe -Wno-trigraphs -fno-
exceptions -fno-rtti -fasm-blocks -g -Os -fmessage-length=0 -mtune=G4
-I/Users/hans/code/pure-data/GemLibs/FTGL/mac/build/FTGL.build/
Default/ftgl.build/ftgl.hmap -Wmost -Wno-four-char-constants -Wno-
unknown-pragmas -F/Users/hans/code/pure-data/GemLibs/FTGL/mac/build/
Default -I/Users/hans/code/pure-data/GemLibs/FTGL/mac/build/Default/
include -IIncludes -I/Users/hans/code/pure-data/GemLibs/FTGL/mac/
build/FTGL.build/Default/ftgl.build/DerivedSources -c /Users/henry/
Development/PROJECTS/FTGL/src/FTBitmapGlyph.cpp -o /Users/hans/code/
pure-data/GemLibs/FTGL/mac/build/FTGL.build/Default/ftgl.build/
Objects-normal/ppc/FTBitmapGlyph.o
powerpc-apple-darwin8-gcc-4.0.1: /Users/henry/Development/PROJECTS/
FTGL/src/FTBitmapGlyph.cpp: No such file or directory
powerpc-apple-darwin8-gcc-4.0.1: warning: '-x c++' after last input
file has no effect
powerpc-apple-darwin8-gcc-4.0.1: no input files
** BUILD FAILED **
g++ -c -I../../include -g -O2 -I/usr/include/freetype2 ../../src/
FTGLTextureFont.cpp -o FTGLTextureFont.o
../../include/FTTextureGlyph.h:55: error: extra qualification
'FTTextureGlyph::' on member 'ResetActiveTexture'
make[1]: *** [FTGLTextureFont.lo] Error 1
make[1]: Leaving directory /home/pd/auto-build/pd-extended/GemLibs/ FTGL/unix/src' make[1]: Entering directory
/home/pd/auto-build/pd-extended/GemLibs/
FTGL/unix/demo'
GLUT not available, demo won't be compiled
Terrorism is not an enemy. It cannot be defeated. It's a tactic.
It's about as sensible to say we declare war on night attacks and
expect we're going to win that war. We're not going to win the war
on terrorism. - retired U.S. Army general, William Odom
Hans-Christoph Steiner wrote:
So the first results are not so promising. It didn't build on either Debian/stable or Mac OS X. Can anyone give me some of the hidden secrets to building FTGL?
if i remember correctly, i have checked in the project-files which were working with some "current" (don't know the version number though) version of xcode. should be in mac/FTGL.xcodeproj/ (instead of mac/FTGL.xcode/) and it should have fixed all the leftovers from the original FTGL-project where there are absolute paths instead of relative ones.
at least it did compile here the last time i tried, without any major issues
mfgas.dr IOhannes
On Apr 20, 2007, at 4:51 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
So the first results are not so promising. It didn't build on either Debian/stable or Mac OS X. Can anyone give me some of the hidden secrets to building FTGL?
if i remember correctly, i have checked in the project-files which
were working with some "current" (don't know the version number though) version of xcode. should be in mac/FTGL.xcodeproj/ (instead of mac/FTGL.xcode/) and it should have fixed all the leftovers from the original FTGL-project where there are absolute paths instead of relative ones.at least it did compile here the last time i tried, without any
major issues
It seems to be missing a header: ft2build.h I can't find this in the
Gem CVS:
/usr/bin/gcc-4.0 -x c++ -arch i386 -pipe -Wno-trigraphs -fno- exceptions -fno-rtti -fasm-blocks -g -Os -fmessage-length=0 -I/Users/ pd/auto-build/pd-extended/GemLibs/FTGL/mac/build/FTGL.build/Default/ ftgl.build/ftgl.hmap -Wmost -Wno-four-char-constants -Wno-unknown- pragmas -F/Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/build/ Default -I../include -I/Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../../freetype-2.2.1/include -I/usr/local/include/freetype2 -I/ Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/build/Default/ include -IIncludes -I/Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/build/FTGL.build/Default/ftgl.build/DerivedSources -c /Users/pd/ auto-build/pd-extended/GemLibs/FTGL/mac/../src/FTBitmapGlyph.cpp -o / Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/build/FTGL.build/ Default/ftgl.build/Objects-normal/i386/FTBitmapGlyph.o In file included from /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../src/FTBitmapGlyph.cpp:3: /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTBitmapGlyph.h:5:22: error: ft2build.h: No such file or directory /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTBitmapGlyph.h:6:10: error: #include expects "FILENAME" or <FILENAME> /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTBitmapGlyph.h:7:10: error: #include expects "FILENAME" or <FILENAME> In file included from /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../include/FTBitmapGlyph.h:10, from /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../src/FTBitmapGlyph.cpp:3: /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTGlyph.h:5:10: error: #include expects "FILENAME" or <FILENAME> /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTGlyph.h:6:10: error: #include expects "FILENAME" or <FILENAME> In file included from /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../include/FTGlyph.h:8, from /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../include/FTBitmapGlyph.h:10,
mfgas.dr IOhannes
I spent 33 years and four months in active military service and
during that period I spent most of my time as a high class muscle man
for Big Business, for Wall Street and the bankers. - General
Smedley Butler
On Apr 20, 2007, at 8:19 PM, Hans-Christoph Steiner wrote:
On Apr 20, 2007, at 4:51 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
So the first results are not so promising. It didn't build on
either Debian/stable or Mac OS X. Can anyone give me some of the hidden secrets to building FTGL?if i remember correctly, i have checked in the project-files which
were working with some "current" (don't know the version number though) version of xcode. should be in mac/FTGL.xcodeproj/ (instead of mac/FTGL.xcode/) and it should have fixed all the leftovers from the original FTGL-project where there are absolute paths instead of relative ones.at least it did compile here the last time i tried, without any
major issuesIt seems to be missing a header: ft2build.h I can't find this in
the Gem CVS:
Ok, I figured it out. It turns out that the Fink package freetype219
(which of course has version 2.2.1) is pretty whack. These two paths
need to be added to the "User Header Search Path" in "Edit Project
Settings" in XCode:
/sw/lib/freetype219/include /sw/lib/freetype219/include/freetype2
Then it works. Could someone commit that change?
.hc
/usr/bin/gcc-4.0 -x c++ -arch i386 -pipe -Wno-trigraphs -fno- exceptions -fno-rtti -fasm-blocks -g -Os -fmessage-length=0 -I/ Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/build/FTGL.build/ Default/ftgl.build/ftgl.hmap -Wmost -Wno-four-char-constants -Wno- unknown-pragmas -F/Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/ build/Default -I../include -I/Users/pd/auto-build/pd-extended/ GemLibs/FTGL/mac/../../freetype-2.2.1/include -I/usr/local/include/ freetype2 -I/Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/build/ Default/include -IIncludes -I/Users/pd/auto-build/pd-extended/ GemLibs/FTGL/mac/build/FTGL.build/Default/ftgl.build/DerivedSources
-c /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../src/ FTBitmapGlyph.cpp -o /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/build/FTGL.build/Default/ftgl.build/Objects-normal/i386/ FTBitmapGlyph.o In file included from /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../src/FTBitmapGlyph.cpp:3: /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTBitmapGlyph.h:5:22: error: ft2build.h: No such file or directory /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTBitmapGlyph.h:6:10: error: #include expects "FILENAME" or <FILENAME> /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTBitmapGlyph.h:7:10: error: #include expects "FILENAME" or <FILENAME> In file included from /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../include/FTBitmapGlyph.h:10, from /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../src/FTBitmapGlyph.cpp:3: /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTGlyph.h:5:10: error: #include expects "FILENAME" or <FILENAME> /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTGlyph.h:6:10: error: #include expects "FILENAME" or <FILENAME> In file included from /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../include/FTGlyph.h:8, from /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../include/FTBitmapGlyph.h:10,mfgas.dr IOhannes
I spent 33 years and four months in active military service and
during that period I spent most of my time as a high class muscle
man for Big Business, for Wall Street and the bankers. -
General Smedley Butler
There is no way to peace, peace is the way. -A.J. Muste
On Apr 20, 2007, at 8:38 PM, Hans-Christoph Steiner wrote:
On Apr 20, 2007, at 8:19 PM, Hans-Christoph Steiner wrote:
On Apr 20, 2007, at 4:51 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
So the first results are not so promising. It didn't build on
either Debian/stable or Mac OS X. Can anyone give me some of the hidden secrets to building FTGL?if i remember correctly, i have checked in the project-files
which were working with some "current" (don't know the version number though) version of xcode. should be in mac/FTGL.xcodeproj/ (instead of mac/FTGL.xcode/) and it should have fixed all the leftovers from the original FTGL-project where there are absolute paths instead of relative
ones.at least it did compile here the last time i tried, without any
major issuesIt seems to be missing a header: ft2build.h I can't find this in
the Gem CVS:Ok, I figured it out. It turns out that the Fink package
freetype219 (which of course has version 2.2.1) is pretty whack.
These two paths need to be added to the "User Header Search Path"
in "Edit Project Settings" in XCode:/sw/lib/freetype219/include /sw/lib/freetype219/include/freetype2
Then it works. Could someone commit that change?
http://sourceforge.net/tracker/index.php? func=detail&aid=1704690&group_id=17203&atid=414256
It turns out that making an FTGL package for Fink was not very hard.
This process made it easier. I figure that GemLibs/FTGL/mac would be
a good place for the ftgl.info file. Could someone check it in there?
.hc
.hc
/usr/bin/gcc-4.0 -x c++ -arch i386 -pipe -Wno-trigraphs -fno- exceptions -fno-rtti -fasm-blocks -g -Os -fmessage-length=0 -I/ Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/build/FTGL.build/ Default/ftgl.build/ftgl.hmap -Wmost -Wno-four-char-constants -Wno- unknown-pragmas -F/Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/build/Default -I../include -I/Users/pd/auto-build/pd-extended/ GemLibs/FTGL/mac/../../freetype-2.2.1/include -I/usr/local/include/ freetype2 -I/Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/ build/Default/include -IIncludes -I/Users/pd/auto-build/pd- extended/GemLibs/FTGL/mac/build/FTGL.build/Default/ftgl.build/ DerivedSources -c /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../src/FTBitmapGlyph.cpp -o /Users/pd/auto-build/pd-extended/ GemLibs/FTGL/mac/build/FTGL.build/Default/ftgl.build/Objects- normal/i386/FTBitmapGlyph.o In file included from /Users/pd/auto-build/pd-extended/GemLibs/ FTGL/mac/../src/FTBitmapGlyph.cpp:3: /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTBitmapGlyph.h:5:22: error: ft2build.h: No such file or directory /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTBitmapGlyph.h:6:10: error: #include expects "FILENAME" or
<FILENAME> /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTBitmapGlyph.h:7:10: error: #include expects "FILENAME" or <FILENAME> In file included from /Users/pd/auto-build/pd-extended/GemLibs/ FTGL/mac/../include/FTBitmapGlyph.h:10, from /Users/pd/auto-build/pd-extended/GemLibs/ FTGL/mac/../src/FTBitmapGlyph.cpp:3: /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTGlyph.h:5:10: error: #include expects "FILENAME" or <FILENAME> /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTGlyph.h:6:10: error: #include expects "FILENAME" or <FILENAME> In file included from /Users/pd/auto-build/pd-extended/GemLibs/ FTGL/mac/../include/FTGlyph.h:8, from /Users/pd/auto-build/pd-extended/GemLibs/ FTGL/mac/../include/FTBitmapGlyph.h:10,
mfgas.dr IOhannes
I spent 33 years and four months in active military service and
during that period I spent most of my time as a high class muscle
man for Big Business, for Wall Street and the bankers. -
General Smedley Butler
There is no way to peace, peace is the way. -A.J. Muste
http://at.or.at/hans/
Ok, last email on the topic ;). I forgot to include in description
in the ftgl.info file. Here is an updated version:
.hc
On Apr 20, 2007, at 10:11 PM, Hans-Christoph Steiner wrote:
On Apr 20, 2007, at 8:38 PM, Hans-Christoph Steiner wrote:
On Apr 20, 2007, at 8:19 PM, Hans-Christoph Steiner wrote:
On Apr 20, 2007, at 4:51 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
So the first results are not so promising. It didn't build on
either Debian/stable or Mac OS X. Can anyone give me some of the hidden secrets to building FTGL?if i remember correctly, i have checked in the project-files
which were working with some "current" (don't know the version number though) version of xcode. should be in mac/FTGL.xcodeproj/ (instead of mac/FTGL.xcode/) and it should have fixed all the leftovers from the original FTGL-project where there are absolute paths instead of relative
ones.at least it did compile here the last time i tried, without any
major issuesIt seems to be missing a header: ft2build.h I can't find this in
the Gem CVS:Ok, I figured it out. It turns out that the Fink package
freetype219 (which of course has version 2.2.1) is pretty whack.
These two paths need to be added to the "User Header Search Path"
in "Edit Project Settings" in XCode:/sw/lib/freetype219/include /sw/lib/freetype219/include/freetype2
Then it works. Could someone commit that change?
http://sourceforge.net/tracker/index.php? func=detail&aid=1704690&group_id=17203&atid=414256
It turns out that making an FTGL package for Fink was not very
hard. This process made it easier. I figure that GemLibs/FTGL/mac
would be a good place for the ftgl.info file. Could someone check
it in there?<ftgl.info>
.hc
.hc
/usr/bin/gcc-4.0 -x c++ -arch i386 -pipe -Wno-trigraphs -fno- exceptions -fno-rtti -fasm-blocks -g -Os -fmessage-length=0 -I/ Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/build/FTGL.build/ Default/ftgl.build/ftgl.hmap -Wmost -Wno-four-char-constants -Wno- unknown-pragmas -F/Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/build/Default -I../include -I/Users/pd/auto-build/pd-extended/ GemLibs/FTGL/mac/../../freetype-2.2.1/include -I/usr/local/ include/freetype2 -I/Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/build/Default/include -IIncludes -I/Users/pd/auto-build/pd- extended/GemLibs/FTGL/mac/build/FTGL.build/Default/ftgl.build/ DerivedSources -c /Users/pd/auto-build/pd-extended/GemLibs/FTGL/ mac/../src/FTBitmapGlyph.cpp -o /Users/pd/auto-build/pd-extended/ GemLibs/FTGL/mac/build/FTGL.build/Default/ftgl.build/Objects- normal/i386/FTBitmapGlyph.o In file included from /Users/pd/auto-build/pd-extended/GemLibs/ FTGL/mac/../src/FTBitmapGlyph.cpp:3: /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTBitmapGlyph.h:5:22: error: ft2build.h: No such file or directory /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTBitmapGlyph.h:6:10: error: #include expects "FILENAME" or
<FILENAME> /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTBitmapGlyph.h:7:10: error: #include expects "FILENAME" or <FILENAME> In file included from /Users/pd/auto-build/pd-extended/GemLibs/ FTGL/mac/../include/FTBitmapGlyph.h:10, from /Users/pd/auto-build/pd-extended/GemLibs/ FTGL/mac/../src/FTBitmapGlyph.cpp:3: /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTGlyph.h:5:10: error: #include expects "FILENAME" or <FILENAME> /Users/pd/auto-build/pd-extended/GemLibs/FTGL/mac/../include/ FTGlyph.h:6:10: error: #include expects "FILENAME" or <FILENAME> In file included from /Users/pd/auto-build/pd-extended/GemLibs/ FTGL/mac/../include/FTGlyph.h:8, from /Users/pd/auto-build/pd-extended/GemLibs/ FTGL/mac/../include/FTBitmapGlyph.h:10,
mfgas.dr IOhannes
I spent 33 years and four months in active military service and
during that period I spent most of my time as a high class muscle
man for Big Business, for Wall Street and the bankers. -
General Smedley Butler
There is no way to peace, peace is the way. -A.J. Muste
http://at.or.at/hans/
Man has survived hitherto because he was too ignorant to know how to
realize his wishes. Now that he can realize them, he must either
change them, or perish. -William Carlos Williams