Oolite Windows - Trunk nightly builds

[Cody]

Thanks Getafix... and a special 'thank you' to your wife!

[Capt. Murphy]

Beware of charming sombreroed contrabandistas thanking your wife. Especially when it's a first post on a new page with no context. Makes you wonder....

[Getafix]

El Viejo??? My wife??? What else am I to offer to the Oolite altar!?!
Hmmm... My mother-in-law, perhaps?!?

[Svengali]

El Viejo??? My wife??? What else am I to offer to the Oolite altar!?!
Hmmm... My mother-in-law, perhaps?!?

Erm... no, no, thanks

[Cody]

El Viejo??? My wife??? What else am I to offer to the Oolite altar!?!
Hmmm... My mother-in-law, perhaps?!?

Well...

[CommonSenseOTB]

El Viejo??? My wife??? What else am I to offer to the Oolite altar!?!
Hmmm... My mother-in-law, perhaps?!?

Well...

Does she do textures? If so then bring her on down.

[JazHaz]

Not used to using trunk, can I ask a silly question?

Can I just take the download and install over my current trunk version to update, or do I have to uninstall first?

[Cody]

Just uninstall first... it'll leave your AddOns and Saves untouched.

[Fatleaf]

But not your keyconfig.plist you will need to copy that over.

[JazHaz]

But not your keyconfig.plist you will need to copy that over.

I already keep that in a Config folder in my Addons folder.

On a similar vein, can I put my .GNUstepDefaults file in my Addons folder somewhere?

Tried when I updated to rev 4663 but it didn't work. I just dropped it into my Addons folder, but not inside a folder.

Its annoying to have to set up trunk for full screen, volume etc etc each time I update it.

[snork]

.. and joystick settings and savegame folder(s) (if you have them outside the default place)

I always copy the whole old backed-up GnuStep folder into any new fresh oolite app folder - done.

[another_commander]

JazHaz: .GNUstepDefaults is supposed to be inside oolite.app\GNUstep\Defaults, not AddOns. Copy it there and you should be OK.

[Kaks]

A nasty regression bug sneaked in today's build - rev4665 - that basically disables Oolite if starting in windowed mode.

Do not dowload, unless you know exactly how to set oolite to always start in fullscreen mode.

[Getafix]

It seems that we have some MS-Trumble building the nightly,
the last successful being for r4668.

I believe that the r4670 "Makefile" is the culprit

Code: Select all

...
[line 112]          rm -idr oolite.app
...
[line 115]          rm -idr AddOns && cd DebugOXP && $(MAKE) clean && cd ..
...

The automated nighlty most probably pauses waiting for user input.
Furthermore... does simple 'rm' works? I thought that "$(RM)" is needed.

I will be able to confirm in 2 to 3 hours, if noone else fries this sooner.

EDIT: The nightly build performs a clean build every night executing:

Code: Select all

$ make -f Makefile clean
$ make -f Makefile pkg-win-snapshot

It's clear that this process freezes prompting:

Code: Select all

$ make -f Makefile clean
make -f GNUmakefile clean
make[1]: Entering directory `/d/myoolite/trunk'
rm -rf ./*~ ./obj
rm -f -rf obj obj.spk obj.dbg obj.spk.dbg
make[1]: Leaving directory `/d/myoolite/trunk'

The oolite.app directory contains settings, logs, savegames and snapshots.
rm -idr oolite.app
rm: remove directory `oolite.app'? 

Cheers!

[Kaks]

Sorry, I did find out the hard way that 'make -f Makefile clean' deletes both log files & test savegames in windows, as well as wiping the AddOns folder - the one I had full of edge case oxps - so I went for the 'confirm before wiping' solution...
I 'cleverly' didn't think of the automated build.

If it's ok with you I'll add another target called fclean (as in force clean).

That way you can set the automated build use fclean to totally wipe those directories, while humans can use clean to just mean 'remove what the compiler put in there, but nothing else', which is more-or-less established practice...

Sounds good?