Ruby Gem for Chipmunk

[banister]

Heya,

great work on Chipmunk and thanks for the ruby bindings, however it's slightly difficult to get chipmunk going for most ruby users. Would it be okay if i released a cross-platform ruby gem for chipmunk?

you can contact me at jrmair@gmail.com

thanks,

banister

[banister]

...I just went ahead and released the gem, hope you dont mind

I set as the homepage a link to the official chipmunk site, you can check out the github project here: http://github.com/banister/chipmunk

To install the gem just go: gem install chipmunk

If there's anything at all you want me to change about the gem or the README or anything at all, just let me know,

EDIT: just letting you know i had to modify the README file as alot of the content there was not relevant to the ruby release

thanks

banister

[slembcke]

That's great. People have been asking about making a gem for a while, but I never looked into what it would take to make one. Maybe you could give me some tips on how to build an extension properly for the trunk version? For our last project, I wanted to try SCons and hacked something together that could build the extension on Windows, Linux, and OS X. I wasn't 100% satisfied with it though.

[banister]

well the best solution by far for building extensions (and gems based on extensions) is to use rake-compiler (http://github.com/luislavena/rake-compiler)
it even cross-compiles to windows (so you can save a tedious reboot and eternal frustration with the microsoft C compiler...which hates c99 btw :/)

If you're interested how to use it, just take a peek at the Rakefile I use in my project (http://github.com/banister/chipmunk)

cheers

[slembcke]

[shawn42]

You should look at using FFI to make this gem more portable.

[shawn42]

I have started to play with FFI and chipmunk bindings..



I have noticed that most of your cpVect class is static inlines, this makes them unavailable for calling via FFI. There are two ways around this:
One, I write all the Vec stuff in Ruby, not a fan of this option as it will be very slow.
Two, I'd like it if you could create a wrapper of all these inline functions that external libs could call. The benefits here would be that all the C chipmunk code could still get the speed of inline calls, and external libs could still call them without having to rewrite them.

[slembcke]

Assuming that you are using GCC, you could compile an empty C file that imports the chipmunk header and use the -fkeep-inline-functions flag. I think that should give you a library that you can link to that has a concrete version of all of the inline functions and nothing else. As there are a lot more inline functions than just the cpVect ops, this would probably be the easiest solution all around.

http://gcc.gnu.org/onlinedocs/gcc/Inline.html

Defining them as extern inline also looks like an option, but it requires you to copy/paste the function and maintain a copy of it in the header and in a module. That sounds rather annoying and I'd probably forget to update both copies. If the above solution works, that would be best.

[slembcke]

[shawn42]

I guess I'm looking for more of a global solution that would be in chipmunk itself. The idea of writing FFI bindings is that the users wouldn't need to custom compile anything.

It'd be great if we could somehow just make those available in the default build of chipmunk. Does that make sense?

PS feel free to shoot me an email or IM at shawn42 __A_T__ gmail