How to build Oolite source on Ubuntu

For discussion of ports to POSIX based systems, especially using GNUStep.

Moderators: winston, another_commander, Getafix

Post Reply
User avatar
wild turkey
Average
Average
Posts: 9
Joined: Thu Jul 10, 2008 3:12 am

Post by wild turkey » Mon Jul 06, 2009 12:55 pm

Just built Oolite 1.72.2 on Ubuntu 9.04 using the instructions from the beginning of this thread with no problems.

Didn't have to rename Linux_All_OPT.OBJ to Linux_All_OPT.OBJ. Think it only needs to be done in trunk for some reason.
Last edited by wild turkey on Tue Jul 14, 2009 9:22 am, edited 1 time in total.
Regards,
WT

zevans
---- E L I T E ----
---- E L I T E ----
Posts: 322
Joined: Mon Jul 06, 2009 11:12 pm
Location: Uncharted backwaters of the unfashionable end of the western spiral arm

Post by zevans » Mon Jul 13, 2009 12:14 pm

I got it built, and it's working. :D

However the only way I could get the Resources loaded was to copy everything in Resources subdir under oolite.app into my .Oolite/AddOns in the home directory. (Cunningly I renamed my 1.72.2 .Oolite out of the way first!)

According to the log it's looking first in /usr/bin/Resources/oolite/Resources, which doesn't make much sense - should we add a step to change this in a header somewhere before compiling?

[Edit for directory paths]

zevans
---- E L I T E ----
---- E L I T E ----
Posts: 322
Joined: Mon Jul 06, 2009 11:12 pm
Location: Uncharted backwaters of the unfashionable end of the western spiral arm

Post by zevans » Wed Jul 15, 2009 12:56 am

For the avoidance of doubt, I trashed both installs (1.72.2 autopackage and the trunk build), moved all my . directories out of the way, and recompiled. Now sure enough it is using the Resources directory under oolite.app correctly. Moral: make sure your system is clean of other Oolite versions before you build.

User avatar
Getafix
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 960
Joined: Tue Apr 01, 2008 12:55 pm
Location: A small ice asteroid, orbiting Oresrati in Galaxy 8 (a.k.a. northwest Armorica).
Contact:

Post by Getafix » Sun Sep 06, 2009 10:25 am

The first post of this thread has been updated for 1.73.2
"Any sufficiently advanced information is indistinguishable from noise." [Newman, Lachmann, Moore]

zevans
---- E L I T E ----
---- E L I T E ----
Posts: 322
Joined: Mon Jul 06, 2009 11:12 pm
Location: Uncharted backwaters of the unfashionable end of the western spiral arm

Post by zevans » Mon Sep 07, 2009 11:48 pm

Since this is specifically for Ubuntu... isn't

Code: Select all

make pkg-deb
once you've pulled the source a lot easier... saves messing around with the Monkey stuff since that all happens magically this way?

User avatar
Micha
Commodore
Commodore
Posts: 815
Joined: Tue Sep 02, 2008 2:01 pm
Location: London, UK
Contact:

Post by Micha » Tue Sep 08, 2009 7:46 am

zevans wrote:Since this is specifically for Ubuntu... isn't

Code: Select all

make pkg-deb
once you've pulled the source a lot easier... saves messing around with the Monkey stuff since that all happens magically this way?
It would be:

Code: Select all

make -f Makefile pkg-deb
since the GNUMakefile (which is the default makefile used) doesn't include the 'pkg-deb' target.

in either case, Getafix's steps are, with a few tweaks, applicable to most Linux distro's, whereas the Makefile currently only caters to Debian-derived systems, hence these steps are still a valuable resource.
The glass is twice as big as it needs to be.

User avatar
Getafix
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 960
Joined: Tue Apr 01, 2008 12:55 pm
Location: A small ice asteroid, orbiting Oresrati in Galaxy 8 (a.k.a. northwest Armorica).
Contact:

Post by Getafix » Wed Sep 23, 2009 8:29 am

First post of this topic has been updated to point 1.73.4.
The section "2.3 Build Oolite" has been simplified.
"Any sufficiently advanced information is indistinguishable from noise." [Newman, Lachmann, Moore]

skoondi
Poor
Poor
Posts: 5
Joined: Wed Sep 02, 2009 3:38 am
Location: Western Australia

subversion update

Post by skoondi » Fri Sep 25, 2009 8:08 am

Hi Getafix thanks for the guide.

I'm fairly new to subversion and I'm wondering if there is a command I can use to update my source which is currently at 173.2 to 173.4. I see that there are instructions for updating to the latest trunk but I don't need bleeding edge, just the most stable test release. I tried some googling but without success.

User avatar
Getafix
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 960
Joined: Tue Apr 01, 2008 12:55 pm
Location: A small ice asteroid, orbiting Oresrati in Galaxy 8 (a.k.a. northwest Armorica).
Contact:

Post by Getafix » Fri Sep 25, 2009 8:35 am

It is suggested to follow the first post steps again, starting from paragraph 2,
considering that you have done the same for 1.73.2.
"Any sufficiently advanced information is indistinguishable from noise." [Newman, Lachmann, Moore]

skoondi
Poor
Poor
Posts: 5
Joined: Wed Sep 02, 2009 3:38 am
Location: Western Australia

Post by skoondi » Fri Sep 25, 2009 4:22 pm

Thanks for the response, I'm assuming that will download the whole lot again which I'm trying to avoid as I'm on a very slow satellite Internet connection.

User avatar
Micha
Commodore
Commodore
Posts: 815
Joined: Tue Sep 02, 2008 2:01 pm
Location: London, UK
Contact:

Post by Micha » Fri Sep 25, 2009 4:42 pm

Hi skoondi,

Did you check out "branches/1.73-maintenance" or "tags/173.2" from Subversion? You can find out by going into your Oolite source directory and typing "svn info" and look at the URL in the information returned.

In the first case, it's quite easy to do, in the second case I'm not sure - at the very least you'd have to play around with the Subversion metadata I think which in general is not a good idea.

Continuing on in the first case, you can either just "svn update" which will get you 1.73.4 + a handful of minor tweaks, or "svn update -r 2579" to get the revision of the source which was tagged as the actual 1.73.4 release.

@Getafix, sorry for stealing your thunder, I know we discussed this issue on IRC, just not sure if you're still around today and I'm away for the rest of the weekend.
The glass is twice as big as it needs to be.

skoondi
Poor
Poor
Posts: 5
Joined: Wed Sep 02, 2009 3:38 am
Location: Western Australia

Post by skoondi » Sat Sep 26, 2009 6:24 am

Hi Micha,

Unfortunately I have the second situation. I will bear it in mind for next time and make sure I check out the maintenance branch. Thanks.

User avatar
Getafix
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 960
Joined: Tue Apr 01, 2008 12:55 pm
Location: A small ice asteroid, orbiting Oresrati in Galaxy 8 (a.k.a. northwest Armorica).
Contact:

Post by Getafix » Sat Sep 26, 2009 10:48 am

First post has been updated to check out from "branches/1.73-maintenance',
to shorten the download time for the next releases.

Cheers.
"Any sufficiently advanced information is indistinguishable from noise." [Newman, Lachmann, Moore]

skoondi
Poor
Poor
Posts: 5
Joined: Wed Sep 02, 2009 3:38 am
Location: Western Australia

Post by skoondi » Sun Sep 27, 2009 8:48 am

For anyone in the same situation as I was, that is having checked out the 1.73.x tagged source and wanting to update it without doing a complete checkoutm the subversion switch command seems to do the trick:

svn switch -r2579 http://svn.berlios.de/svnroot/repos/ool ... intenance/

Just did this and all seems good, now have 1.73.4

User avatar
foxbow
Harmless
Harmless
Posts: 1
Joined: Thu Nov 12, 2009 9:10 am
Location: .de

Thanks for the work

Post by foxbow » Thu Nov 12, 2009 9:18 am

Just want to blurt out my happiness :D

First I have built the standard source pack and ended up with no sound. Next time I just followed this how-to and ended up with a fully working oolite on my Ubuntu 9.10 Karmic box.

And sound can be crucial when it comes to reacting to incoming missiles..

However building the .deb files could work smoother. Using
# dpkg-buildpackage
will complain about missing debian/changelog file and
# make -f Makefile dpkg
will build the changelog file but bail out due to a missing 'debuild' utility. However afterwards the dpkg-buildpackage worked fine and now I can upgrade the other machine as well.

Great work!
There is no safe distance...

Post Reply