Any one up for OSX work.

Return to Compiling or Editing the Panda Source

Postby kaweh » Tue Jun 13, 2006 4:45 am

hi there,

i've now created a page with collected instructions and a binary package for Panda3D (the instructions do not include the means to compile Panda3D yourself, i will add that later for people interested - until then you have to dig through this thread).

have a look at http://knuddl.net/moin.cgi/InstallPanda3d

please be aware that this is totally experimental! if you do not follow the instruction as exactly as possible the package won't probably work. use at your own risk! this is not an official package, but hacked together by myself to make it easier for me to install Panda3D on other Macs. you still need to use the terminal for various parts.

the package reflects the result of this thread. there is a second thread here with a patch by tetious, which i have already applied to my private workspace but not yet to the binary package. this will give us shader support and most of the pandatools. i need to clean this up a little and i hope to contribute a patch back to Panda3D with all of this.

i am hoping to improve the package over time. so stay tuned for a new version within a couple of days (can't give an ETA sorry - this is a hobby project of mine).

hope that helps,
kaweh

you can reach me at: kaweh (at) knuddl (dot) net - please be aware that i can't give any support - the package is "as is". i'm interested in any feedback. if i can help and time permits, i will certainly do so.
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby kaweh » Wed Jun 14, 2006 11:48 am

[edit] - this can be ignored now. mayald was using gcc 3.3 to link instead of gcc 4.0 as the rest. i fixed mayald and am a happy person now.

-------------------------------

now i try to build the pandatools. so far i was able to build most of them.

now i try to build the maya tools (linking against Maya 7.0 - on OS X) but i fail.

any idea how this could be resolved?

Code: Select all
ld: Undefined symbols:
__ZN10TypeHandle5_noneE referenced from libegg expected to be defined in libinterrogatedb.dylib
__ZN11TypedObject12_type_handleE referenced from libegg expected to be defined in libinterrogatedb.dylib
__ZN11TypedObject9init_typeEv referenced from libegg expected to be defined in libinterrogatedb.dylib
__ZN11TypedObjectD2Ev referenced from libegg expected to be defined in libinterrogatedb.dylib
__ZN12TypeRegistry13register_typeER10TypeHandleRKSs referenced from libegg expected to be defined in libinterrogatedb.dylib
__ZN12TypeRegistry15is_derived_fromE10TypeHandleS0_P11TypedObject referenced from libegg expected to be defined in libinterrogatedb.dylib
__ZN12TypeRegistry17record_derivationE10TypeHandleS0_ referenced from libegg expected to be defined in libinterrogatedb.dylib
__ZN12TypeRegistry3ptrEv referenced from libegg expected to be defined in libinterrogatedb.dylib
__ZNK12TypeRegistry8get_nameE10TypeHandleP11TypedObject referenced from libegg expected to be defined in libinterrogatedb.dylib
__ZTI11TypedObject referenced from libegg expected to be defined in libinterrogatedb.dylib
__Z24init_system_type_handlesv referenced from libexpress expected to be defined in libinterrogatedb.dylib
__ZN12TypeRegistry21record_alternate_nameE10TypeHandleRKSs referenced from libputil expected to be defined in libinterrogatedb.dylib
__ZN10MutexDebug10do_releaseEv referenced from libputil expected to be defined in libpipeline.dylib
__ZN10MutexDebug7do_lockEv referenced from libputil expected to be defined in libpipeline.dylib
__ZN10MutexDebugC2ERKSsb referenced from libputil expected to be defined in libpipeline.dylib
__ZN10MutexDebugD2Ev referenced from libputil expected to be defined in libpipeline.dylib
__ZN12TypeRegistry18get_parent_towardsE10TypeHandleS0_P11TypedObject referenced from libputil expected to be defined in libinterrogatedb.dylib
__ZN12TypeRegistry21register_dynamic_typeERKSs referenced from libputil expected to be defined in libinterrogatedb.dylib
__ZN6Thread12_main_threadE referenced from libputil expected to be defined in libpipeline.dylib
__ZN6Thread16init_main_threadEv referenced from libputil expected to be defined in libpipeline.dylib
__ZN9CycleData17complete_pointersEPP13TypedWritableP9BamReader referenced from libputil expected to be defined in libpipeline.dylib
__ZN9CycleData6fillinER16DatagramIteratorP9BamReader referenced from libputil expected to be defined in libpipeline.dylib
__ZN9CycleData6fillinER16DatagramIteratorP9BamReaderPv referenced from libputil expected to be defined in libpipeline.dylib
__ZN9CycleDataD2Ev referenced from libputil expected to be defined in libpipeline.dylib
__ZNK10MutexDebug6outputERSo referenced from libputil expected to be defined in libpipeline.dylib
__ZNK12TypeRegistry16get_parent_classE10TypeHandlei referenced from libputil expected to be defined in libinterrogatedb.dylib
__ZNK12TypeRegistry22get_num_parent_classesE10TypeHandleP11TypedObject referenced from libputil expected to be defined in libinterrogatedb.dylib
__ZNK12TypeRegistry9find_typeERKSs referenced from libputil expected to be defined in libinterrogatedb.dylib
__ZNK9CycleData14write_datagramEP9BamWriterR8Datagram referenced from libputil expected to be defined in libpipeline.dylib
__ZNK9CycleData14write_datagramEP9BamWriterR8DatagramPv referenced from libputil expected to be defined in libpipeline.dylib
__ZNK9CycleData6outputERSo referenced from libputil expected to be defined in libpipeline.dylib
__ZTI10MutexDebug referenced from libputil expected to be defined in libpipeline.dylib
__ZTI9CycleData referenced from libputil expected to be defined in libpipeline.dylib
__ZTV11TypedObject referenced from libputil expected to be defined in libinterrogatedb.dylib
/usr/bin/libtool: internal link edit command failed
make[1]: *** [Opt2-osx/libmayaegg.dylib] Error 1
make: *** [install-mayaegg] Error 2


thanks,
kaweh
Last edited by kaweh on Fri Jun 16, 2006 10:15 am, edited 1 time in total.
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby kaweh » Thu Jun 15, 2006 6:38 pm

A new version 0.3 of the Panda3D for Mac OS X package is available here.

Changes:

* Updated to latest CVS.
* Linked against the Cg Framework, shader support is enabled! If you upgrade from 0.2 to 0.3 you have to install the Cg Framework (instructions on page).
* Includes many Panda3D tools (see list on page).
* Added correct license to installer, improved installer.

Enjoy,
Kaweh

[Edit] New samples archive has been uploaded too now, including some of the shader samples.

[Edit] The patch against current CVS head can be found here: http://knuddl.net/Panda3D_MacOSX_0.3.patch. The used Config.pp can be found here: http://knuddl.net/Config.pp
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby kaweh » Fri Jun 16, 2006 3:23 pm

Hey there,

is there a way to tell ppremake to generate Makefiles that strip the resulting *.dylib/*.so from symbols?

Thanks,
Kaweh
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby drwr » Fri Jun 16, 2006 3:35 pm

In the Linux case, it simply doesn't pass -g to the compiler when OPTIMIZE=4, which achieves the same effect. (See the definition for CFLAGS_OPT1/2/3/4 in dtool/Config.pp).

I suspect the OSX ppremake scripts may not be set up to do the equivalent thing properly. Is there a compiler option on OSX, similar to -g, to avoid putting the symbols there in the first place? You can experiment with customizing your CFLAGS variable to see if you get this effect.

David
drwr
 
Posts: 11425
Joined: Fri Feb 13, 2004 12:42 pm
Location: Glendale, CA

Postby kaweh » Fri Jun 16, 2006 4:01 pm

Thanks David. I'm currently using OPTIMIZE=2, I'll give OPTIMIZE=4 a try and will look into Config.pp/Config.osx.pp.
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby kaweh » Fri Jun 16, 2006 5:25 pm

Well, OPTIMIZE 4 compiles fine, but makes pview and custom code crash with:

/usr/local/panda/include/deletedChain.T:117: failed assertion `orig_flag == (PN_int32)DCF_alive'
Abort trap

I assume that the gcc 4.0 optimization in this case is a tad to aggressive? ;)

Anyways I go back to OPTIMIZE 2 (and hand edited Config.pp to obmit the -g flag) for now. Nothing I will keep anyways for longer, just want to see the difference in size.

Thanks for the tip, David.

Cheers,
Kaweh
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby kaweh » Wed Jun 28, 2006 1:44 pm

A new version of the "Panda3D for OS X" package is available:

http://knuddl.net/moin.cgi/InstallPanda3d

Changes:

* Maya support and more tools added (bash configuration needs to be updated to make this work).
* Fixed keyboard support (the Escape key is now working as expected).
* Added mousewheel support.
* Package size reduced (the package only includes the stripped libraries).

Please let me know if you run into any problems.

Cheers,
Kaweh
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Panda3d on OSX-Intel

Postby psederberg » Sun Jul 23, 2006 10:59 pm

First off, thanks to everyone working on the OSX port of Panda3D.

My lab is quite interested in using Panda3D for running VR experiments to study spatial navigation, however, OSX/Intel support is a key.

We currently do most of our development in python, which is why Panda3D seems like the perfect fit.

Is there any reason why Panda3D would not compile with the Universal Cg-1.5 release from nVidia? It seems like that is the only non-universal dependency...

Also, I know that no one is working on sound, but shouldn't it be possible to get it working because it is based on the fmod api, which runs on OSX.

Thanks again,
Per
psederberg
 
Posts: 2
Joined: Sun Jul 23, 2006 10:21 pm

Postby kaweh » Mon Jul 24, 2006 4:14 am

both shouldn't be a problem really (famous last words).

i just didn't have the time to come around to create a Intel version and downloading/installing/re-compiling with fmod.

intel version shouldn't be to far away, i'm planning to release a new version within the next week and might have time to try to get a Intel build up and running, too.

i didn't yet use Cg 1.5 because at that time i created the package it was still in beta (as far as i remember).

essentially as soon as you got the compiling process running on OS X, it's not a big deal to get other packages in (though i struggled a litte while with Maya and the compile process).

cheers,
kaweh
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby psederberg » Mon Jul 24, 2006 11:52 pm

Dear Kaweh:

Thanks for the (encouraging) information!

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.

Latro,
P
psederberg
 
Posts: 2
Joined: Sun Jul 23, 2006 10:21 pm

Postby anomaly » Thu Aug 31, 2006 11:48 am

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 >_<

Any ideas/success stories from anyone else?

Thanks
anomaly
 
Posts: 2
Joined: Tue Aug 29, 2006 12:30 pm

Postby kaweh » Fri Sep 01, 2006 10:12 am

A new version of the Panda3D on Mac OS X package is now available:

http://knuddl.net/moin.cgi/InstallPanda3d

New in this version:

Now builds for PPC and new Intel-based Macs available!
Updated to lastest CVS head revision.
Various dependencies/packages updated.
Removed fftw (see http://panda3d.org/phpbb2/viewtopic.php?t=1568).
Compiled against FMOD Ex (though this is currently not working as intended).

Enjoy,
Kaweh
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby kaweh » Fri Sep 01, 2006 10:15 am

psederberg wrote: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.


You are right, I wanted to do this for a long time now. Something I need to find time to get around. CVS, ugh! :)

Anyways, I hope the new package with the Intel Mac build is somehow helpful.

Cheers,
Kaweh
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby kaweh » Fri Sep 01, 2006 10:20 am

anomaly wrote:Has anyone had any luck with panda3d on an intel mac yet? Any ideas/success stories from anyone else?


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).

Cheers,
Kaweh
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Yes!

Postby anomaly » Fri Sep 01, 2006 10:38 am

It works and we have a very happy faculty member :)

Thank you very much!
anomaly
 
Posts: 2
Joined: Tue Aug 29, 2006 12:30 pm

Installing trouble

Postby Hypnos » Tue Sep 05, 2006 3:40 am

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.
Hypnos
 
Posts: 585
Joined: Sat Sep 11, 2004 8:07 am
Location: Zürich, Switzerland

Postby kaweh » Fri Sep 08, 2006 3:03 pm

i'm posting this into the sticky thread again, so this information doesn't get lost.

there is a hack for the 0.5 build to enable FMOD Ex on OS X.

see http://www.panda3d.org/phpbb2/viewtopic.php?p=8440#8440

cheers,
kaweh
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby bigfoot29 » Mon Oct 16, 2006 2:42 am

No problem. The sticky is here because OS X work might get "lost" otherwise.
So, of course, you can use this for announcing news as well. :D

Can someone tell (in short words) the status of the OS X - port?
0.5 is the current release? Whats working? Or in case thats less: whats not? :)

Regards, Bigfoot29
User avatar
bigfoot29
 
Posts: 618
Joined: Thu Jun 30, 2005 4:22 am
Location: Germany

Postby kaweh » Mon Oct 16, 2006 4:20 am

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 ;)

cheers,
kw.
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby drwr » Mon Oct 16, 2006 6:33 am

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?

David
drwr
 
Posts: 11425
Joined: Fri Feb 13, 2004 12:42 pm
Location: Glendale, CA

Postby kaweh » Mon Oct 16, 2006 6:42 am

drwr wrote: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.


i'm really happy to hear that!

Kaweh--what kind of mousewheel problems did you have? Would you mind sharing your fixes with us?


mouse-wheel was not implemented in some version (see history on the wiki).

i would definitely be happy to provide my changes and support the OS X version.

i will update to latest CVS later this week and create a patch including my changes. where should i send it?

cheers,
kaweh
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby drwr » Mon Oct 16, 2006 11:13 am

You can send it to me via email. Let me know if you experience problems with merge conflicts on the latest CVS.

David
drwr
 
Posts: 11425
Joined: Fri Feb 13, 2004 12:42 pm
Location: Glendale, CA

Postby kaweh » Fri Oct 27, 2006 1:18 pm

I haven't forgotten about your request David, just a busy time right now.

I want to release a new version of my package anyways with Josh releasing Panda3D 1.3.0 - so that might be a good point to create a patch.

Josh, do you tag the CVS repository with the 1.3.0 release, i might just grab that tag and go from there?

Cheers,
Kaweh
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby Josh Yelon » Mon Oct 30, 2006 11:20 am

Yes. There is a tag "panda3d_1_3_0" in there. There's also "panda3d_1_3_branch" which is a branch tag.
Josh Yelon, Teacher, Carnegie Mellon Entertainment Technology Center
Josh Yelon
 
Posts: 1360
Joined: Wed Mar 30, 2005 8:30 pm

Postby drwr » Tue Oct 31, 2006 5:26 pm

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.

David
drwr
 
Posts: 11425
Joined: Fri Feb 13, 2004 12:42 pm
Location: Glendale, CA

Postby kaweh » Tue Oct 31, 2006 6:13 pm

thanks david. i didn't get around to try anything yet. sorry.
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby kaweh » Thu Nov 02, 2006 9:43 am

Hi David,

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.

Code: Select all
cd ./src/dtoolbase && make all
cc   -c -o Opt2-osx/dtoolbase_dlmalloc.o -I. -I/Users/kaweh/Projects/panda3d/dtool   -D_DEBUG -Wall -g -O2 -fPIC dlmalloc.c
cc   -c -o Opt2-osx/dtoolbase_lookup3.o -I. -I/Users/kaweh/Projects/panda3d/dtool   -D_DEBUG -Wall -g -O2 -fPIC lookup3.c
CC   -c -o Opt2-osx/dtoolbase_indent.o -I. -I/Users/kaweh/Projects/panda3d/dtool   -D_DEBUG -Wall -g -O2 -fPIC indent.cxx
CC   -c -o Opt2-osx/dtoolbase_dtoolbase_composite1.o -I. -I/Users/kaweh/Projects/panda3d/dtool   -D_DEBUG -Wall -g -O2 -fPIC dtoolbase_composite1.cxx
CC   -c -o Opt2-osx/dtoolbase_dtoolbase_composite2.o -I. -I/Users/kaweh/Projects/panda3d/dtool   -D_DEBUG -Wall -g -O2 -fPIC dtoolbase_composite2.cxx
CC -shared  -o Opt2-osx/libdtoolbase.dylib Opt2-osx/dtoolbase_dlmalloc.o Opt2-osx/dtoolbase_lookup3.o Opt2-osx/dtoolbase_indent.o Opt2-osx/dtoolbase_dtoolbase_composite1.o Opt2-osx/dtoolbase_dtoolbase_composite2.o -L/usr/local/panda/lib
powerpc-apple-darwin8-gcc-4.0.1: unrecognized option '-shared'
/usr/bin/ld: Undefined symbols:
_main
std::ios_base::Init::Init()
std::ios_base::Init::~Init()
std::basic_ostream<char, std::char_traits<char> >& std::operator<< <std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char)
___gxx_personality_v0
std::cerr
std::basic_ostream<char, std::char_traits<char> >& std::operator<< <std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*)
collect2: ld returned 1 exit status
make[1]: *** [Opt2-osx/libdtoolbase.dylib] Error 1
make: *** [dtoolbase] Error 2


i also know what the problem is. if we look at dtool/scr/dtoolbase/Makefile lines 37-38 it says:

Code: Select all
Opt2-osx/libdtoolbase.dylib : $(libdtoolbase_so)
    CC -shared  -o Opt2-osx/libdtoolbase.dylib $(libdtoolbase_so) -L/usr/local/panda/lib


now this is wrong on OS X. to link correctly it needs to say

Code: Select all
Opt2-osx/libdtoolbase.dylib : $(libdtoolbase_so)
    g++ -dynamiclib  -o Opt2-osx/libdtoolbase.dylib $(libdtoolbase_so) -L/usr/local/panda/lib


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

Code: Select all
#define OPTIMIZE 2

#define HAVE_GL 1

#define HAVE_CG 1
#define HAVE_CGGL 1

#define HAVE_MAYA 1
#define MAYA_LOCATION /Applications/Alias/maya7.0/devkit

#define INSTALL_PYTHON_SOURCE 1
#define HAVE_PYTHON 1
#define PYTHON_FRAMEWORK /Library/Frameworks/Python.framework

#define ALTERNATIVE_MALLOC
//#define DO_MEMORY_USAGE

#define ZLIB_IPATH /opt/local/include
#define ZLIB_LPATH /opt/local/lib

#define JPEG_IPATH /opt/local/include
#define JPEG_LPATH /opt/local/lib

#define PNG_IPATH /opt/local/include
#define PNG_LPATH /opt/local/lib

#define TIFF_IPATH /opt/local/include
#define TIFF_LPATH /opt/local/lib

#define FFMPEG_IPATH /opt/local/include/ffmpeg
#define FFMPEG_LPATH /opt/local/lib

#define HAVE_FMODEX 1
#define FMOD_IPATH /Users/kaweh/Projects/fmod/api/inc
#define FMOD_LPATH /Users/kaweh/Projects/fmod/api/lib

#define PRC_PATH_ENVVARS CFG_PATH ETC_PATH
//#define DEFAULT_PATHSEP : :
kaweh
 
Posts: 173
Joined: Thu Mar 30, 2006 7:15 am
Location: Vienna, Austria

Postby drwr » Thu Nov 02, 2006 1:13 pm

Have you checked out and built a current version of ppremake? You should see something like this in response to ppremake -V:
Code: Select all
newt:~> ppremake -V
This is ppremake version 1.22 built on Oct 20 2006 at 09:59:04.
Default platform is "OSX".

David
drwr
 
Posts: 11425
Joined: Fri Feb 13, 2004 12:42 pm
Location: Glendale, CA

Postby kelly » Tue Nov 28, 2006 3:39 pm

i saw toontown online was released for Mac. Is panda3d using different code?
kelly
 
Posts: 10
Joined: Mon May 08, 2006 4:46 pm

PreviousNext

Return to Compiling or Editing the Panda Source

Who is online

Users browsing this forum: No registered users and 0 guests