New release: ODE 0.12
Daniel K. O.
It took a long time, but it's here. ODE 0.12:
http://sourceforge.net/projects/opende/files/ODE/0.12/
Among the changes, we have:
* Better compilation support for various platforms.
* Built-in python bindings.
* New primitive colliders privded by libccd (see
http://ode-wiki.org/wiki/index.php?title=Manual:_Collision_Detection#Collision_tests_supported)
* Many bug fixes and optimizations.
A more detailed changelog is available at
http://ode-wiki.org/wiki/index.php?title=Changelog
Once again I would like to express my gratitude to the whole ODE
community, for helping us making it better. In particular for Oleh's
significant work on code optimization and cleanup, Gideon Klompje's
python bindings, Daniel Fiser's libccd, and all the bug and patch
submitters.
I apologize for holding this one out for so long; the delay was mostly
my fault for wanting to test and fix more than my schedule allowed. I
hope to roll out minor releases much faster from now on.
--
Daniel K. O.
Danny Price
> --
> You received this message because you are subscribed to the Google Groups "ode-users" group.
> To post to this group, send email to ode-...@googlegroups.com.
> To unsubscribe from this group, send email to ode-users+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ode-users?hl=en.
>
Danny Price
After three years of having to mess around in order to build ODE on the mac, this is indeed a wonderful thing.
Question about the demos - they are predominately 'pure' C (which is good as ODE's primary API is C) but have .cpp extensions. I made an effort to clean them up in the past but the .cpp extension means that C++ code has snuck in there. The new Tracks demo is the same.
Is there a reason for this?
On 11 Feb 2012, at 23:39, Daniel K. O. wrote:
Daniel K. O.
> Just downloaded this on OSX Snow Leopard and it all built out of the
> box!
>
> After three years of having to mess around in order to build ODE on
> the mac, this is indeed a wonderful thing.
I'm glad it worked. From the horror stories I heard from coworkers it's
not a small feat.
> Question about the demos - they are predominately 'pure' C (which is
> good as ODE's primary API is C) but have .cpp extensions. I made an
> effort to clean them up in the past but the .cpp extension means that
> C++ code has snuck in there. The new Tracks demo is the same.
>
> Is there a reason for this?
From my part, it's mostly for creating variables where I think they make
sense; I also find cout/clog to be more convenient to dump data than printf.
What would the benefits of a 100% pure C demo be?
--
Daniel K. O.