[Odejava] native code - should we turn on debug?

Game Mechanics
#1

Currently the Win32 and Linux binaries are compiled in Release mode, while the newly added OSX are in Debug mode. The debug ones can warn about ODE problems (such as doing stuff in the wrong order) and have the full method symbols used for stack traces (depending on your JVM, this can point you to the native method which caused the crash, even if that method was called from another native method. This is the case with the Apple JVM).

I am thinking it’s probably a good idea to publish both versions, would people use them if we did? Is it wise to use CVS for this? The debug binaries can be about five times the size, and CVS isn’t really meant for that. Is this a good time to start distributing the compiled binaries only though the file sharing section?

Will.

#2

As a developer, having access to the debug versions would be nice. Especially if there’s a chance we can get debug output related to order of operations. I agree CVS is not the place for the binaries though.

If you put ODE binaries in the filesharing section, you need to make it VERY clear as to which versions of odejava they work, and you should probably do ‘official’ releases of odejava more often (at least as often as the binary updates) and put them in the filesharing area too. Since the binaries will be a seperate download, you don’t want users scratching their heads trying to figure out which binary/java combo works. Make it stupid obvious.

-Tab

#3

Yeah I think it would be great to have debug version easily available. My program at the moment is in the 1 in 5 crashing stage at the moment and I would love to know why.

#4

[quote]Yeah I think it would be great to have debug version easily available. My program at the moment is in the 1 in 5 crashing stage at the moment and I would love to know why.
[/quote]
And a fun stage that is ::slight_smile:

Tonight I’ll try and get a debug version out + update the JWS.

Will.