Chipmunk Physics

Hello,

I am sorry if this is a repeat post, but the other posts on troubles installing chipmunk in xcode havent really been helpful. I am new to osx/xcode, so maybe its where my stupidity is coming into place.

I've downloaded the latest version, unpacked it all and I am able to get the xcode project building at the very least, but when i try to import chipmunk into my own workspace, i get a lot of compile errors.

I've added the .c/.h files from the /src directory and the /include into 'other sources' within xcode and I've also added the constraints directory, but it seems like it cannot find a lot of the header files. A good example is that chipmunk.c is unable to find a .h file in the constraints directory, despite that i am looking right at it. Am i not supposed to add the constraints directory as a group? I've also made sure I have select 'copy files into workspace' when adding them.

I am starting to run into a brick wall on this, but I am obviously doesnt something incorrect. Also, I'm doing this for a mobile project, so linking a static library is apparently a big no-no on that, so if there is a way to do it adding the source directly, any help would be much appreciated. Hopefully its something as easy as changing a few compile options hehe.

Thank you for your help in advance!

From the readme:

iPhone: If you want a native Objective-C API, check out the Objective-Chipmunk directory for the Objective-C binding and some sample code from shipping iPhone Apps. It is inexpensive to license and should save you a lot of time. Otherwise, the XCode project can build a static library with all the proper compiler settings. Alternatively, you can just run iphonestatic.command in the macosx/ directory. It will build you a fat library compiled as release for the device and debug for the simulator. After running it, you can simply drop the Chipmunk-iPhone directory into your iPhone project!

slembcke,

Thank you for the quick reply, but I was looking to do some work for the palm pre, not the iphone. Id imagine it is slightly different to setup that environment. Any ideas?

Ah. I didn't even realize that you could use Xcode to do Pre development.

Are you sure you can't link to a static library? Do you know why? That seems very odd to me. Mobile platforms often disallow dynamic linking, but a static library is basically just a zip-like file of the compiled .o files. Compiling it as a static library makes it much easier to deal with getting all the optimizations flags correct and separate from the rest of your project.

Xcode is really dumb about automatically setting up header include paths correctly when you import code. I always set the header search paths in the build settings by hand.

perhaps I was getting confused about the static vs dynamic libraries. but yes you can use xcode for pre dev hehe. Am I just able to make the static libraries using cmake? (sorry, I am new to osx/xcode). I will also give setting the header search path a shot. I had to do that for the pdk anyways hehe.

thanks!

I'm not sure how you would tell the CMake files to build against the Pre SDK, but it can probably be done. I would make a separate static library target inside your project, or a separate project entirely to build the static lib.