I’ll keep my eye’s peeled for the new release. You are correct that the Universal Cg version (1.5) is still in beta, but it seems to be the only option if Panda3D is gonna run on an IntelMac.
If you get the chance to supply your current patches to get things compiling in general (i.e., what you did so far), I’d be happy to give it a whirl on my macbook and try to work through any intel compile issues.
Has anyone had any luck with panda3d on an intel mac yet? Using the universal Cg 1.5 etc I was able to build everything just fine, and I can run pview with -h and get the help out so the command itself is working, but whenever I try to have it display anything graphically the process ends with a kill() at the top of the stacktrace; I’m guessing the problem with this lies somewhere outside of panda3d. After giving up on this route, I compiled again on another intel mac and got to the same point, only this time the error was that there was that my libTIFF.dylib did not have a symbol in libpandagl.dylib (__cg_tiffseterrorhandler) if i remember correctly.
So yes, in both instances I got panda to compile just fine, but I could never use pview >_<
Now builds for PPC and new Intel-based Macs available!
Updated to lastest CVS head revision.
Various dependencies/packages updated.
Removed fftw (see discourse.panda3d.org/viewtopic.php?t=1568).
Compiled against FMOD Ex (though this is currently not working as intended).
Try my new build and let me know how it goes. I got pview running and my test programs did run without any issues as far as I could see (though I haven’t tested the Intel version extensivly).
While trying to install the package i encountered a problem. If you get the errormessage “sie können nicht fortfahren. Es ist keine Software zum installieren vorhanden” (in english something like “No Software found to install”) You have to remove any remaining Panda3d-x.x.pkg file in the folder /Library/Receipts. This solved my problem, hope this helps someone else as well.
i’m using the version on a daily basis and i didn’t yet encounter any problems which are Panda3D + OS X specific (well i had one with mouse-wheel support, but i fixed that).
though rendering with the windows version is a lot faster, but this is probably due to slower OpenGL drivers on OS X.
using Panda3D on my G5, MacBook Pro with OS X, and MacBook Pro with Windows gives very different results regarding performance (MacBook Pro with Windows/OpenGL by far the fastest).
other than that, i’m developling on OS X and my collegues on PC and we are fine.
i would like to sync a new release with Josh, but probably not before end of november because i’m too busy right now.
if you encounter any problems - and maybe include a tester that proves this is an Panda3D + OS X specific problem - i will try to look into these.
and i would wish that installation would be easier, but that’s a totally different project in intself
Also, FYI, we have recently gotten a lot more serious in the VR Studio about developing for the Mac, and we have begun aggressively checking in fixes for OSX development as well.
Kaweh–what kind of mousewheel problems did you have? Would you mind sharing your fixes with us?
Note that, unfortunately, many of the recent OSX fixes we have been developing in the VR Studio haven’t made it under the 1.3.0 tag, or even onto the 1.3 branch. It didn’t seem like a good idea to destabilize the Windows port while we were developing OSX.
By now, the CVS trunk is pretty stable for both Windows and OSX, but it has moved on a bit from the 1.3.0 version.
I am trying to get the OS X version to run from a clean CVS trunk (i have backed-up my previous version). you did a lot of changes, and i rather try to get the current CVS trunk to run correctly on OS X and create a patch from there instead going from a 2 month old version.
currently I hit a wall as soon as i try to make dtool.
i assume this is because ppremake is using the unix template for generating the Makefile… i don’t see a OS X template. calling CC on C++ code is also odd as far as i can tell.
do you know which *.pp file i should try to fix and see if i can get the current clean CVS trunk to build correctly?
thanks,
kaweh
ps: this is my current local LOCAL_PPREMAKE_CONFIG