[GEM-dev] OSX Compiled but not working

[B. Bogart]

hey Wesley,

I modified that project a couple times for vertex arrays and for this
spotlight thing so I may have messed something up. I don't recall the
setup.h files...

What OS are you running? 10.3.7? Totally up-to-date? Could these symbols
be stuff missing from an older system? Since Chris said the orb stuff
does not work in OSX then you can just remove those files that refer to it.

the Gem OSX developers use project builder (still?) rather then the
newer Xcode. If I knew how to deal with the linking I would have solved
it by now. I assume it should do it automatically when you include a
static lib in the frameworks.

A makefile to compile Gem from terminal would be really handy,
especially for package build systems. The reason why there is none is
that most users just want a binary on OSX, ie not linux savvy users.
Also because there are very few (what 5?) people who actually compile
Gem on OSX. I think it would be a great contribution and I can tell you
I sure would use the command line build!!!

Note that makefiles on OSX are different than on linux, so you would
need to know all the OSX weirdness with gcc and so on. ranlib(),
-frameworks etc.. headers and libs are treated differently on OSX than
other platforms. It *should* not be hard to make the compilation, but
then I don't think anyone has started doing it...

Anyhow try updating your machine (and dev-tools maybe??) and then get
rid of the orb stuff and see what happens. I did have a problem
compiling vertex-arrays I think, because my AGL was too old.

B.

Wesley H. Smith wrote:
> Thanks for the xcode project Ben,
>
> I compiled your project.  You had a setup.h for each folder in the Gem/src
> folder.  I didn't have those files, so I took them out of the project.  The Gem
> binary ended up being 2.3MB, and when I tried to run it with PD, I got some more
> undefined symbols.
>
> __ZN8CVector39normalizeEv
> __ZN8CVector3C1Efff
> __ZN8CVector3C1Ev
> __ZN8CVector3miES_
> __ZN8CVector3plES_
> _orb_close
> _orb_getstatus
> _orb_init
> _orb_open
> _orb_set_nullregion
> pd_gui: pd process exited
>
> How was the G4 optimized GEM build created?  with the Xcode project?  If so, how
> does one specify for libraries to statically link?  I'm really tempted to just
> use the command line to compile this thing.  If I have everything in place like
> this, it shouldn't be as difficult as it is to compile.  Of course, I'm pretty
> new to this kind of thing, so I may be off base there.
>
> wes
>
>
>
> Quoting "B. Bogart" <ben at ekran.org>:
>
>
>>Here is my Xcode project, I'm not sure if it'll be of any use since it
>>seems Xcode uses absolute paths by default.
>>
>>Also my Gem is much smaller, and as I realized its because my freetype
>>is not staticallly linked, even though I have the libfreetype.a in my
>>frameworks. Maybe yours is also dynamically linking to some things,
>>explaining the size difference.
>>
>>It took me months and lots of help from Jamie and Chris to get Gem
>>compiling. :(
>>
>>One of these days I'll look into a command line build... ah but when.
>>
>>My "user" name is "admin" and you can just remove the spotlight.cpp and
>>spotlight.h references.
>>
>>B.
>>
>>Wesley H. Smith wrote:
>>
>>>Thanks for the tip on the src files James,
>>>
>>>So, I was able to compile Gem.pd_darwin with one caveat...my Gem.pd_darwin
>>
>>is
>>
>>>12.6MB whereas the G4 distribution is 17.9MB.  Obviously, something went
>>
>>wrong
>>
>>>here.  For grins, I tried to run PD/GEM with the version I compiled.  PD
>>>loaded, I saw the console window and then it quit without saying anything
>>
>>not
>>
>>>even about GEM.  I thent tried it with the G4 distro from iem and
>>
>>everything
>>
>>>was normal.  At this point, I have no idea what went wrong.  I have all of
>>
>>the
>>
>>>files/frameworks etc.  The last thing I was having problems with was trying
>>
>>to
>>
>>>get Xcode to find libftgl.a.  I gave the project a path to this file in the
>>>resource path settings and it compiled.
>>>
>>>I did do one thing that I wasn't sure about.  I made an errant click in the
>>>xcode project, but I wasn't sure what exactly I did.  I ended up getting
>>
>>some
>>
>>>erorrs that I hadn't seen before and unchecked gemextwin.cpp and
>>
>>gemextwin.h
>>
>>>from the project since they included /Base/GemOutput.h.
>>>
>>>During compilation I had 41 warnings which looked mostly harmless to me
>>
>>from
>>
>>>tube.h, pix_texture.cpp, pix_halftone.cpp, model_loader.cpp,
>>
>>GemPixUtil.cpp,
>>
>>>and pix_videoDarwin.cpp.
>>>
>>>Maybe someone has come across this situation before?
>>>Any suggestions?
>>>
>>>
>>>best,
>>>wes
>>>
>>>_______________________________________________
>>>GEM-dev mailing list
>>>GEM-dev at iem.at
>>>http://iem.at/cgi-bin/mailman/listinfo/gem-dev
>>>
>>
>
>
> _______________________________________________
> GEM-dev mailing list
> GEM-dev at iem.at
> http://iem.at/cgi-bin/mailman/listinfo/gem-dev
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20050327/6c76bb92/attachment.pgp>