[ODE] Official ODE Bindings for .NET 2.0?

[Terry L. Triplett]

The Tao (the whole project, not just Tao.Ode) build system is
autotools-based, and is .NET 2.0 only in SVN head.  You could look there for
inspiration - it's geared for cross-platform compatibility, so you'll find
all the tests to configure for .NET and Mono builds.

Since ODE's build system is autotools based, it should be simple enough to
add the .NET stuff to the existing build system, if that's what you want.

It might be easier, though, to keep the C/C++ and .NET builds separate to
avoid complicating things, given that the .NET bindings don't need to know
anything about the C/C++ side of things at build time.  Since the binding
happens at run-time, all that really should be required is that the native
ODE library has been built - and then only if you want to run something
(like tests).  It should be simple enough to check for the ODE shared
library in the standard build output location, and complain and abort if
it's not there (or bootstrap the native build, I suppose).

On 9/8/06, Jason Perkins <starkos at gmail.com> wrote:
>
> A couple of issues that I am facing with the .NET bindings, in case
> anyone has advice to offer...
>
> I'm not sure how to integrate it with the build system, or if I even
> should. It requires .NET 2.0 so that rules out all but VS.NET 2005 and
> the GNU tools. I'm inclined to say "just drop these files into your
> project and build".
>
> Related, I'd like to port several (all?) of the tests to C# in order
> to test the bindings, but that means that I need some kind of parallel
> build system. Right now I am relying on premake to build the scripts
> (so I can build on both Linux and Windows).
>
> Any ideas appreciated,
>
> Jason
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://q12.org/pipermail/ode/attachments/20060908/d79ee548/attachment.htm