[odejava] Updating Linux natives

Game Mechanics
#1

Hello!

I’m trying to update my odejava Linux natives using the description on the odejava.org homepage (the “Docs” tab, the “Compiling/Updating Odejava Natives”). However, the description is either very old or just not working for me :slight_smile:

I’m using Fedora Core 3, if that’s of any interest. Let’s see what I’ve tried, and what doesn’t quite seem to work for me:

1: Grab latest ODE CVS: No problem.
2: Apply cylinder2 contrib patch: Don’t know how to do it. I try to “cd contrib/dCylinder2/”, and then “patch dcylinder2.patch”, but it does nothing. I’ve tried other invocations of the “patch” command as well, but none seem to work.
3: Apply Makefile patch: Where can I find it?
4: Edit user.settings: I suppose it should read “copy config/user-settings.example to config/user-settings, edit so the correct operating system and debug mode is selected”. No problem.
5: Just run make-gcc: make-gcc doesn’t seem to be a standard part of Fedora Linux, so I just try “make” and “gmake”. None of these make the compilation work.

One of my problems is that the ODE makefile assumes that I have already compiled OPCODE, but OPCODE is, as far as I can see, in a Windows-only state in ODE’s CVS repository. Perhaps the “Makefile patch” solves this for me, if I can find it?

Please please please, can anybody help me here? :slight_smile: I guess somebody must have been able to do it before :wink:

Thanks in advance,
Ole

PS: If you’re wondering why I’d like to update the odejava natives, it’s because the trimesh collision doesn’t seem to work for me. I’m writing a game with a car (made out of a box and 4 spheres, just like the Ode and Odejava-xith3d demos) on some ramps (made out of trimeshes), and my car falls through a lot of the trimeshes. Not all of them, but about half of them. All trimeshes have the same size and orientation, so it doesn’t seem to be a problem related to size, as some of you have in another thread in this forum. Since some fixes to trimeshes have been submitted to the Ode CVS, I thought it might be worth a try.

#2

d’oh, “make-gcc” is a shell script of ours, you run it like so:


./make-gcc

:slight_smile:

It is highly likely that when recompiling against new ODE sources, you need to change parts of the SWIG interface, java code and even the make files as the ODE API changes. The process is not one I recommend for people new to either ODE or Odejava, but good luck :slight_smile:

Will.

#3

Hi William!

Thanks for the reply. I’ve still got no clue as to how to apply the cylinder2 patch, and where in the world I should get the Makefile patch, but this is a start :wink:

Fiddling a little with the sources once I get the build environment working is no problem. I’m not new to C or Java, I just have a problem with makefiles - they sometimes seem to live their own life. (I like Ant a whole lot more!) Besides, I thought the Odejava build process was simple, i.e. simple enough that somebody had made it automatic. But I seem to be wrong.

On a slightly related note, are there any plans for a new “real” Odejava release? Seeing that the newest release is from the 30th of October, and quite a few small fixes have been applied to the Ode CVS repository, I guess other people than me could use a freshly built Odejava.

Ole

#4

[quote]Hi William!

Thanks for the reply. I’ve still got no clue as to how to apply the cylinder2 patch, and where in the world I should get the Makefile patch, but this is a start :wink:

Fiddling a little with the sources once I get the build environment working is no problem. I’m not new to C or Java, I just have a problem with makefiles - they sometimes seem to live their own life. (I like Ant a whole lot more!) Besides, I thought the Odejava build process was simple, i.e. simple enough that somebody had made it automatic. But I seem to be wrong.

On a slightly related note, are there any plans for a new “real” Odejava release? Seeing that the newest release is from the 30th of October, and quite a few small fixes have been applied to the Ode CVS repository, I guess other people than me could use a freshly built Odejava.

Ole
[/quote]
There is an install guide in the wiki, have you read it?

A new build of the Odejava natives is planned this forghtnight.

Will.

#5

Hi William!

Yes, I read the Wiki page (I assume you mean the OdeJava Wiki page). That’s the page I’m referring to in my first posting in this thread. Since the Odejava homepage is down today, I haven’t been able to check if it’s had any updates since my last check, though.

BTW, compiling odejava (not ODE, or the OdeJava natives, but the pure Java part) directly after checking it out from CVS isn’t possible, since some XODE classes require Xerces in the classpath. It’s something that should probably be fixed. Either by altering the Ant buildfile (but then again, the CVS repository should include some Xerces jar files that the buildfile can refer to), ripping out XODE to a separate package (I’d go for this if I were in charge), or using an XML parser that comes with J2SE (com.sun.org.apache.xerces seems to come with J2SE 5, I don’t know if it’s part of J2SE 1.4 as well).

Anyway, just a few thoughts.

Kind regards,
Ole