Debug OXP status

[maik]

Does anyone what the status of the [wiki]Debug OXP[/wiki] is? Oolite complains that it doesn't work with the current version. I left it in the 'normal' section of the [wiki]OXP List[/wiki] because I assumed Ahruman would eventually take care of it but I have a hunch that this is not going to happen anytime soon. Is it even still needed? Or has it been incorporated into Oolite proper?

Thanks for enlightening me.

[Ironfist]

maik,
By current version do you mean 1.75.3? I f so this is because the requires.plist contains the following line: { version = "1.75.4"; max_version = "1.75.4.99"; }
which as you can see is set for the current series of trunk builds. It does run with all of them and is packaged in the trunk build packages. I suspect that if the first number was changed to 1.75.3 that would stop the error from occurring - but what would be a the point the deployment version does not have the debug data compiled in.

Hope this helps
Ironfist

[Eric Walch]

Does anyone what the status of the [wiki]Debug OXP[/wiki] is? Oolite complains that it doesn't work with the current version.

The Mac version of the console is much more integrated in Oolite than for the console for the other platforms and has much directer access to Oolites data. Result is that a slight change in Oolite can lead to crashes when using a different version of the console. Therefor the strict version numbering that does not work between build versions were I did suffer crashes in the past because of using a not-matching version . However that should be no real problem. Every time one compiles Oolite, a new matching version of the debug console is also compiled. It is also distributed with every mac Nighty. I assume when a new version of Oolite is released that wiki link will be updated.

Mac Only:
To make sure I always use the correct version of the console, I have all my oxp's installed in the 'application support' area of the users library. All my different Oolite versions I now store in separate folders together with a addOns folder with only the matching [wiki]Debug OXP[/wiki] in it. These folders are either in the programs area for release versions or in the compiler area for work in progress.
That way I avoid crashes when switching between trunk and release versions. Although I suspect that all 1.75 versions should work with the same console version.

[maik]

Hmm, I only downloaded new Oolite versions by using the built in updater (on OS X) recently. Does this maybe result in Debug OXP not being updated? My requires.plist indeed mentions 1.75.1 while I am on 1.75.3

[Eric Walch]

Good question. The last 2 times I also updated my normal Oolite with the built-in automatic updater. My Debug OXP has the correct version but I am not sure I updated it manually. I can't remember I did, but the creation date of Oolite is the day of the release announcement and that is the day I updated. But the Debug OXP has a creation date that lies 13 days later, somehow suggesting I manually interfered.

And as the built-in updater is mainly intended for normal users, its good possible that the console is excluded. However, I have no idea were in the code this function is build in, so I can't verify.