Elite Wiki - User contributions [en]

OXP

2026-07-23T05:01:37Z

Hiran: /* Creating an OXP */

[[Image:oolite-oxp-icon.png|128px|right|OXP icon]]
An '''OXP''' ('''O'''olite e'''X'''pansion '''P'''ack) is an enhancement to the game [[Oolite]]. An OXP could be a new game object (such as a ship, space station or a moon), a mission, or a combination of several elements. OXPs can use all of the facilities of Oolite, including some that are not used in the standard, unexpanded game. Please note that if you run Oolite in 'Strict Play' mode (set via pressing F2 when docked or paused and then selecting 'Reset to Strict play'), OXPs are not loaded.

An '''OXZ''' is an OXP in a particular '''Z'''ipped format to make it easier for Oolite to process and for players to install - to find out what's inside one, use your unzipping tool of choice on it.

== Finding OXPs ==
=== OXPs ===
*The '''[[OXP List]]''' provides the most comprehensive list of Oolite OXP expansion packs.
*[[Guide to Unlisted OXPs]] has another 200 or so (which are not listed elsewhere).

These have to go into your AddOns folder (see below).
=== OXZs ===
*The [http://www.oolite.space/oxps/#oxp '''OXZ List'''] provides the most comprehensive list of Oolite OXZ expansion packs (but only those uploaded to the in-game Expansions Manager).
*Just for fun, the [[Index of artefacts]] provides the most comprehensive analysis of these Oolite OXZ expansion packs...
*there are just a handful of OXZs (mostly experimental, but including some excellent ones by phkb) not listed on the Expansions Manager/OXZ List. They are mostly in the [[Guide to Unlisted OXPs]] mixed in with everything else.
*Check out the [[Oolite Starter]] which makes management of the expansions in your Ooniverse refeshing like a sip of properly chilled gin and tonic.

Those in the in-game Expansions Manager should go in your Managed AddOns folder. Those which are not should go in your AddOns folder. See below.

=== Old versions ===
For purely historical purposes (or a touch of nostalgia if you've been around Oolite for a long time) you might want to look at [http://oosat.alioth.net The Oolite Satellite Resource Site] ('''Oosat2''', quite broken but still accessible, 2006-11-04 until 2007-03-03) or the even older [http://capnhack.com/hosting/oolite/Oolite/OoSat.html Captain Hack OoSat Site] ('''Oosat1''', beginning until 2006-10-14). Oosat may have originally been hosted here on Alioth.net, as was '''Oldsat'''. They had a tendency to go off-line or to crash, losing all information. Search on the BB if you are curious!

For your curiosity and maybe one or the other odd find there is also the [[OXP Attic]] which houses derelict OXPs from times long past. Also see [https://bb.oolite.space/viewtopic.php?f=2&t=20721 Recovering Lost Oxp's].

== OXPs suitable for new players ==


Everyone has their own idea of what OXPs should be in a starter pack, or which are just best. There are several threads on the Forum on this topic, perhaps the best-balanced and most useful for newcomers being [https://bb.oolite.space/viewtopic.php?f=2&t=11885 this one].

== Suitability for simpler or for more difficult/advanced gaming ==
There exists a way of marking an OXP's difficulty level according to the author's belief. You can find the [[OXP_Levelindicators|level indicators]] on the wiki.

Another system in progress is [[Template:IconOXP]].

==Player recommendations==
These commanders have put together lists of their personal favourites:
*[[User:Cpt|Cpt]] (2013)
*[[User:JazHaz|JazHaz]] (2013)
*[[User:Zireael|Zireael]] (2014)
*[[User:Norby#Recommended_OXPs|Norby]] (2015-7): includes packages of recommended OXPs for new players, the more experienced ''etc''.
*[[User:CaptSolo|CaptSolo]] (2020)

== Help with OXPs ==

Information on OXPs can also be found on the [https://bb.oolite.space/viewforum.php?f=4 Expansion Pack Forum], the Friendliest Board This Side of Riedquat. The helpful people there will be happy to assist you with any questions you have about OXPs.

== Tweaking your OXPs ==
Do you prefer a louder ''beep'' for audible docking clearance? Would you rather your Commander's Log also recorded purchases & repairs? Do you want your Laser Booster to activate automatically upon launch?

You will find recipes for modifying some of the OXPs [https://bb.oolite.space/viewtopic.php?p=216177#p216177 here].

== Installing an OXP ==

OXPs are installed to the folder or directory ('folder' and 'directory' are synonyms) named '''AddOns'''. Read on, we will also tell you where to find that folder.

=== In OXZ format ===
Download the OXZ file, and save it to your AddOns folder.

Many OXZ format expansion packs can also be downloaded and installed for you from the [[Expansions Manager]] in Oolite. These will be placed in a separate folder which Oolite manages ('''ManagedAddOns''') - any you download yourself should go in the '''AddOns''' folder so that Oolite doesn't accidentally overwrite them.

If you want to inspect an OXZ you've downloaded with the expansion pack manager, copy it out of the '''ManagedAddOns''' folder first, then open it with your unzipping program. Some versions of the Expansions Manager can do this for you when you press the ''x'' key.

=== In OXP format ===
Typically, an OXP is downloaded as a ZIP file though occasionally other compression tools such as 7z or rar have been used. Unzip it to find a folder with a name ending .oxp

After unzipping the file, make sure that it is ''only'' the OXP folder that put into the AddOns directory - some zipped OXPs can contain a top level folder with a readMe file, and the actual OXP folder is a level further down. If this is the case, move the folder with the '''.oxp''' extension into the AddOns folder.

Sometimes the zipped files contain several folders, make sure you only copy the folder -or file for Macintoshes- ending with '''.oxp''' into the AddOns folder. This folder is found in different locations, depending on the platform.

If you have followed these instructions and OXPs are not being recognised by the game make sure that your commander is a normal game. If you started your commander using the "Strict Mode" starting option, no OXPs will ever be used.

== Locating your AddOns folder ==

=== Mac OS X ===
Found in the folder that contains the Oolite application. 

Alternatively you can also have the '''AddOns''' folder in your user area at '''~/Library/Application Support/Oolite/AddOns/'''. When both places contain an '''AddOns''' folder, both contents are read with the content in the user libraries loading last.

'''Troubleshooting:''' If you get an error saying "The item could not be moved because "AddOns" cannot be modified", that can happen if you weren't the user that installed Oolite.
The solution is to put the OXPs of your choice in '''~/Library/Application Support/Oolite/AddOns/''' instead (you may need to create this folder).
The error could also be triggered because you’re running from the disk image, you’ll need to copy the game somewhere else. Having done so, if you still get the error, use the Get Info command on the AddOns folder, open the Ownership & Permissions pane and check that it says You Can: Read & Write.

=== Linux ===
The location of the AddOns folder will depend on whether you chose to install Oolite to 'Home' or 'System'.

If you chose the 'Home' installation, the AddOns directory is located in '''~/GNUstep/Applications/Oolite/AddOns'''. The AddOns folder should be in the top level of the Oolite install directory (at the same level as the oolite.app folder) You may have to create it.

If you chose the 'System' installation, the AddOns directory will be '''~/.Oolite/Add-ons'''. You may have to create it. Note that this is a 'hidden' directory, and so you may have to turn on 'Show hidden files' in your file manager before you can see it.

An alternative location for a 'System' installation is the '''/opt/Oolite/AddOns''' directory, but most users find this less convenient than '''~/.Oolite/Add-ons'''.

=== Windows ===
The AddOns folder should be in the top level of the Oolite install directory (at the same level as the oolite.app folder). Historical: if you are using the GNUStep dedicated versions (pre-Jan 2006), then the AddOns folder must be created inside the oolite.app folder.

== Caveats ==
If you purchase a ship that is an OXP ship and save the game, you will only be able to load that commander as long as this OXP is installed in AddOns. If it's not, Oolite will give you an error instead of trying to load the commander.

== Managing a stable of OXPs ==
Nowadays we download OXZs through the in-game Expansions Manager - and it manages them for us. But if we tweak one, it usually becomes an OXP and must then be kept in the AddOns folder. Some older oxps have yet to be turned into OXZs and some experimental OXPs are in a similar position.

So, if you have large numbers of these oxps, see the following threads from the BB.
*Issues with multiple expansions? [[Find the culprit]]
*Issues with [https://bb.oolite.space/viewtopic.php?p=273473#p273473 single OXPs]
*Issues with [https://bb.oolite.space/viewtopic.php?p=273490#p273490 multiple OXPs]
*Issues with different copies of the game on the [https://bb.oolite.space/viewtopic.php?p=272073#p272073 same hard drive]
*If you found a nice set of expansions and want to share that with others, consider using the [[Oolite Starter]]. It allows you to export and send expansion sets to other players, who then can activate it on their side.

== Diagnostics ==
With some OXPs installed, the directory structure will look something like this: 
:'''...\AddOns\Basic-debug.oxp''' 
:'''...\AddOns\Cabal_Common_Library1.5.1.oxp''' 
:'''...\AddOns\Explorers'_Club_1.3.1_2012-01-21.oxp''' 
:'''...\AddOns\halsis.oxp''' 
:'''...\AddOns\Material Test Suite v1.2.oxp''' 
with other directories and files under each of the .oxp directories. You should only find .oxp directories immediately under a \AddOns directory.

If none of your OXPs are working, are you playing in Strict Mode? Try starting a new commander from the Normal Start and see if the OXPs work then.

If you edit the contents of one of your OXPs and cannot see the change, restart Oolite holding down <Shift> to force Oolite to re-read all the OXP files.

If an OXP you installed is not working or is misbehaving, check the [[Latest.log]] file - you should see a list of the OXPs you have installed. You should see a trend in the names which will tell you if you have installed an OXP within another OXP (move it) or two versions of an OXP (remove the older one) or it is absent suggesting you put it in the wrong place or did not get the .oxp directory extension correct (did you unzip the OXP?).

If you know how, a system-wide search for any directory ending in ".oxp" should pull up the OXPs you have installed and they should only appear immediately beneath a '''\AddOns''' directory and never inside another .oxp directory (this is an easily-done error when extracting a zip file).

Note that an OXP in the AddOns folder ''trumps'' an 'identical' OXZ in the ManagedAddOns folder. So if the OXP is an older version, it will [https://bb.oolite.space/viewtopic.php?p=218632#p218632 disable] the newer OXZ.

=== AppleMacs ===
... Strict semicolon parsing is a Mac thing. Windows and Linux use GNUstep to parse plists and that apparently is more relaxed syntax-wise than whatever it is that the Mac uses.
::[[User:Another_commander|Another_commander]] from [https://bb.oolite.space/viewtopic.php?p=262814#p262814 A possible solution?] (2018).

... the libraries in the Mac seems to be less tolerant of some things than the GNUStep libraries on Linux:
:*lists are enclosed in ''''('''' '''')'''' with items separated by '''','''' and there must ''not'' be a comma after the last item in the list.
:*objects are enclosed in ''''{'''' ''''}'''' and consist of pairs: <key> = <value>.
:*Each key/value pair must have a '''';'''' at the end, even the last pair in the object
:*''if'' the object is a value in a key/value pair in another object, it's closing ''''}'''' must be followed by a '''';''''.
::lifted from a PM from [[User:Dybal|Dybal]] (2020)

== Creating an OXP ==
[[File:Plist-XML-ASCII-ill.png|thumb|right|702px|XML (left) & OpenStep (right)]]
Legacy script comes in two versions: XML & OpenStep. And then there is the much more complex Javascript.

It is intended to be easy to create expansion packs. OpenStep is relatively easy - XML and Javascript less so.

=== Start your own OXP ===

There are two quite extreme ways to go, and a compromise:

* OXZs are just renamed zipped OXPs. You can decompress any existing OXZ, look inside and start tweaking.
* And you can start from scratch by creating everything yourself - this will take some advanced knowledge.
* There also is the middle path - to follow our predefined paths and use a bunch of templates.

We have provided three varieties which your OXP can be. Advanced OXP creators can also combine them into a single OXP, while even more advanced creators keep them separate and then link them using dependencies. We'll cover that later.

So what style of OXP is on your mind? Take one of the guided tours:

*[[Create_Ship_OXP|Ship]]
*[[Create_Equipment_OXP|Equipment]]
*[[Create_Mission_OXP|Mission]]

Alternatively, or when curious take a look at the [[OXP howto|OXP Howto]] page for full background information.

=== OXP resources ===
*Here is an [[index of artefacts]] already created in OXPs.
*[[Documenting your artefacts]] (OXP, ships and equipment)
*[[OXP howto]]
*[[Publishing your OXP]]

*[https://github.com/cim--/oxp-build-scripts OXP Packaging Scripts] Cim's collection for Linux (2015)
*[https://bb.oolite.space/viewtopic.php?p=275434#p275434 What can OXP's ''not'' change?] (2021)

Older OXPs (from [[User:Aegidian|Aegidian]]'s day were written in [[Legacy Scripting]]. Modern OXPs are written in JavaScript. Specifically oolite.jsVersion 185, an Oolite specific variant of '''ECMAv5'''. It is the same Spidermonkey version (1.8.5 - March 2011) that Firefox 4 shipped with many years ago, but it is a special build for Oolite. This is the version that we have almost always had and it has not changed between versions of the game. It is unlikely to change in the future (due to the [https://bb.oolite.space/viewtopic.php?p=256623#p256623 immense amount of work] involved in tampering with it!).

=== Troubleshooting ===

Regularly check the Oolite logfile. There are two such files in your filesystem: Latest.log and Previous.log.
TODO: Where exactly to find them?

In case you see Oolite complaining about parsing problems on plist files, this usually raises the question which file Oolite was parsing at that moment. There are lots of such files, and to keep logs short that information is not printed. But you can change the logging configuration. Put a logcontrol.plist file straight into your AddOns folder and Oolite will pick it up. It can be as simple as

{
plist.information = yes;
}

== Loading Order of OXPs ==
OXPs loaded after other OXPs will "trump" the earlier OXPs in terms of their effects on the game. It is a similar situation with the vanilla game code, where the OXPs trump or overwrite the relevant sections of the basic oolite game. 
The loading order under Macs and Windows is alphabetical, while Linux is unpredictable. There is no solution for Linux load ordering as yet ([https://bb.oolite.space/viewtopic.php?p=261821#p261821 Svengali 2018]).

*[[Handling OXP Dependencies with JavaScript]] - how to determine the loading order
*[https://bb.oolite.space/viewtopic.php?p=189416#p189416 Nested OXP's in AddOns folder] (2012)
*[https://bb.oolite.space/viewtopic.php?p=231750#p231750 Cim on the subject] (2015)
*[https://bb.oolite.space/viewtopic.php?f=4&t=8928 OXP loading order] discussion, including Ahruman on the subject (2011)

== AddOns and Managed AddOns folders ==
All versions of Oolite have an AddOns folder. Only versions 1.79 (2013) and onwards have the Managed AddOns folder.

The contents of the '''AddOns folder''' must ''not'' be zipped if they are to be recognised by Oolite - so OXZs will not work if they are in there.

The contents of the '''Managed AddOns''' folder must contain a [[Manifest.plist]] if they are to be recognised by your [[Expansions Manager]] (or by [[Oolite Starter]]). The Expansions Manager only checks ''this'' folder, not the AddOns folder.

== OXP Lists ==
*[http://www.oolite.org/oxps/ Expansion Manager OXZ list] - orderable
*[[OXP List]] - orderable
*[[Guide to Unlisted OXPs]] - with links at the bottom to older lists

*[[Brilliant but broken...]] great oxp's that need updating/fixing... (do you have the skills?)

[[Category:Oolite expansion packs]]
[[Category:Factual]]

Oolite build system

2026-07-13T05:51:44Z

Hiran:

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

Oolite will get built in different scenarios: Developers obviously download the source code from the central repository, apply changes and eventually push their changes back to the repository. Likely they will not run the complete packaging for multiple operating systems. That is where the CI pipeline kicks in on Github: every push triggers a CI build which builds Oolite, performs standard tests and packages it in various formats such that it can easily be used by others. This will work for a defined set of operating systems. Distro packagers like the AUR build will create even more comfort for users by creating OS distribution specific packages. It means Oolite can be installed through the operating system's package managers.

Below you find activity diagrams and a table explaining the purpose of each step. Note that each step may require items to already exist and on the other hand may provide output to other steps.

<gallery>
File:Plantuml-Developer.png|Developer
File:Plantuml-CI.png|CI (on Github)
File:Plantuml-AUR.png|AUR Packager
</gallery>

{| class="wikitable" style="margin:auto"
|-
! Build Step !! Description !! Requires !! Provides
|-
| configure system manually || A developer will maintain his development system will all the required tools and dependencies to build Oolite. Should be supported by scripts. || nothing || configured system
|-
| checkout code || Clone and checkout from the Oolite git repository so it resides in the local filesystem. || configured system || working tree
|-
| change code || A developer will change code in the local filesystem to whatever extent. || working tree || modified working tree
|-
| meson setup || || working tree || meson configuration files
|-
| meson compile || || meson configuration files || compiled and linked output in the build directory
|-
| test/debug manually || A developer will test manually, focusing on the changes he/she applied. || compiled and linked output in the build directory || nothing
|-
| meson test || runs predefined tests || compiled and linked output in the build directory || error log and return status code
|-
| meson install || copies Oolite files to another location on disk || compiled and linked output in the build directory || files in new output location
|-
| meson uninstall || reverse opertion for meson install. Removes the files from the new output location || files in new output location || nothing
|-
| push changes || Push the changes back into the Oolite repository. Likely involves commit and pull request actions. || modified working tree || unmodified working tree
|-
| configure system automatically || Similar to the `configure system manually` step, in CI builds all this has to be scripted. || nothing || configured system
|-
| calculate version number || Generates the checked out version's semver. || working tree ||
|-
| generate tar.gz || Generates an Oolite distribution as tar ball. || compiled and linked output in the build directory || the tar.gz file
|-
| generate AppImage || Generates a Linux AppImage. || the tar.gz file || the AppImage
|-
| generate Flatpak || Generates a Linux Flatpak image. || the tar.gz file || the Flatpak
|-
| generate MSIX || Generates a Windows installer for Oolite using MSIX. || the tar.gz file || the MSIX package
|-
| generate NSIS || Generates a Windows installer for Oolite using NSIS. || the tar.gz file || the executable installer
|-
| tag source code || The CI run will tag the version in the official repository so it is available to all other steps. || the version number || tagged git revision
|-
| upload artifacts || Uploads generated artifacts to a Github Release so they are available to the public. || any kind of artifact || artifacts attached to the release on Github
|-
| prepare || Similar to the `configure system automatically` step, this step will prepare an AUR build environment to build Oolite. || nothing || configured system
|-
| pkgver || Checks the version tag of the local source code and transforms it from semver to an AUR package version number. || working tree || version used by archlinux pacman (package manager) to track installed packages
|-
| package || Generates the AUR package. |||| tarball with files the application needs in a format designed for use by pacman
|-
| publish on AUR || Pushes the AUR package into the AUR repository. || write access on aur package repo for oolite / oolite-git package || shares recipe (PKGBUILD) to build oolite / oolite-git packages on archlinux user systems
|}

{
"builder": "unknown",
"title": "Oolite core",
"version": "1.93.1-190",
"source": "https://github.com/OoliteProject/oolite/releases/tag/1.93.1-190",
"built-at": "2026-07-12T19:59:09+0200",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/",
"expansion_catalog": "https://addons.oolite.space/api/1.0/overview/"
}

Oolite build system

2026-07-13T05:40:53Z

Hiran:

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

<gallery>
File:Plantuml-Developer.png|Developer
File:Plantuml-CI.png|CI (on Github)
File:Plantuml-AUR.png|AUR Packager
</gallery>

{| class="wikitable" style="margin:auto"
|-
! Build Step !! Description !! Requires !! Provides
|-
| configure system manually || A developer will maintain his development system will all the required tools and dependencies to build Oolite. Should be supported by scripts. || nothing || configured system
|-
| checkout code || Clone and checkout from the Oolite git repository so it resides in the local filesystem. || configured system || working tree
|-
| change code || A developer will change code in the local filesystem to whatever extent. || working tree || modified working tree
|-
| meson setup || || working tree || meson configuration files
|-
| meson compile || || meson configuration files || compiled and linked output in the build directory
|-
| test/debug manually || A developer will test manually, focusing on the changes he/she applied. || compiled and linked output in the build directory || nothing
|-
| meson test || runs predefined tests || compiled and linked output in the build directory || error log and return status code
|-
| meson install || copies Oolite files to another location on disk || compiled and linked output in the build directory || files in new output location
|-
| meson uninstall || reverse opertion for meson install. Removes the files from the new output location || files in new output location || nothing
|-
| push changes || Push the changes back into the Oolite repository. Likely involves commit and pull request actions. || modified working tree || unmodified working tree
|-
| configure system automatically || Similar to the `configure system manually` step, in CI builds all this has to be scripted. || nothing || configured system
|-
| calculate version number || Generates the checked out version's semver. || working tree ||
|-
| generate tar.gz || Generates an Oolite distribution as tar ball. || compiled and linked output in the build directory || the tar.gz file
|-
| generate AppImage || Generates a Linux AppImage. || the tar.gz file || the AppImage
|-
| generate Flatpak || Generates a Linux Flatpak image. || the tar.gz file || the Flatpak
|-
| generate MSIX || Generates a Windows installer for Oolite using MSIX. || the tar.gz file || the MSIX package
|-
| generate NSIS || Generates a Windows installer for Oolite using NSIS. || the tar.gz file || the executable installer
|-
| tag source code || The CI run will tag the version in the official repository so it is available to all other steps. || the version number || tagged git revision
|-
| upload artifacts || Uploads generated artifacts to a Github Release so they are available to the public. || any kind of artifact || artifacts attached to the release on Github
|-
| prepare || Similar to the `configure system automatically` step, this step will prepare an AUR build environment to build Oolite. || nothing || configured system
|-
| pkgver || Checks the version tag of the local source code and transforms it from semver to an AUR package version number. || working tree || version used by archlinux pacman (package manager) to track installed packages
|-
| package || Generates the AUR package. |||| tarball with files the application needs in a format designed for use by pacman
|-
| publish on AUR || Pushes the AUR package into the AUR repository. || write access on aur package repo for oolite / oolite-git package || shares recipe (PKGBUILD) to build oolite / oolite-git packages on archlinux user systems
|}

{
"builder": "unknown",
"title": "Oolite core",
"version": "1.93.1-190",
"source": "https://github.com/OoliteProject/oolite/releases/tag/1.93.1-190",
"built-at": "2026-07-12T19:59:09+0200",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/",
"expansion_catalog": "https://addons.oolite.space/api/1.0/overview/"
}

File:Plantuml-Developer.png

2026-07-13T05:38:09Z

Hiran:

File:Plantuml-CI.png

2026-07-13T05:37:34Z

Hiran:

File:Plantuml-AUR.png

2026-07-13T05:36:46Z

Hiran:

File:Build system old.png

2026-07-13T05:32:29Z

Hiran: Hiran moved page File:Build system.png to File:Build system old.png: We have new images

== Summary ==
PlantUML diagram for the build process for developers, CI and AUR distro packagers

File:Build system.png

2026-07-13T05:32:29Z

Hiran: Hiran moved page File:Build system.png to File:Build system old.png: We have new images

#REDIRECT [[File:Build system old.png]]

Oolite build system

2026-07-12T17:59:33Z

Hiran:

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

[[File:Build system.png|frameless|center]]

{| class="wikitable" style="margin:auto"
|-
! Build Step !! Description !! Requires !! Provides
|-
| configure system manually || A developer will maintain his development system will all the required tools and dependencies to build Oolite. Should be supported by scripts. || nothing || configured system
|-
| checkout code || Clone and checkout from the Oolite git repository so it resides in the local filesystem. || configured system || working tree
|-
| change code || A developer will change code in the local filesystem to whatever extent. || working tree || modified working tree
|-
| meson setup || || working tree || meson configuration files
|-
| meson compile || || meson configuration files || compiled and linked output in the build directory
|-
| test/debug manually || A developer will test manually, focusing on the changes he/she applied. || compiled and linked output in the build directory || nothing
|-
| meson test || runs predefined tests || compiled and linked output in the build directory || error log and return status code
|-
| meson install || copies Oolite files to another location on disk || compiled and linked output in the build directory || files in new output location
|-
| meson uninstall || reverse opertion for meson install. Removes the files from the new output location || files in new output location || nothing
|-
| push changes || Push the changes back into the Oolite repository. Likely involves commit and pull request actions. || modified working tree || unmodified working tree
|-
| configure system automatically || Similar to the `configure system manually` step, in CI builds all this has to be scripted. || nothing || configured system
|-
| calculate version number || Generates the checked out version's semver. || working tree ||
|-
| generate tar.gz || Generates an Oolite distribution as tar ball. || compiled and linked output in the build directory || the tar.gz file
|-
| generate AppImage || Generates a Linux AppImage. || the tar.gz file || the AppImage
|-
| generate Flatpak || Generates a Linux Flatpak image. || the tar.gz file || the Flatpak
|-
| generate MSIX || Generates a Windows installer for Oolite using MSIX. || the tar.gz file || the MSIX package
|-
| generate NSIS || Generates a Windows installer for Oolite using NSIS. || the tar.gz file || the executable installer
|-
| tag source code || The CI run will tag the version in the official repository so it is available to all other steps. || the version number || tagged git revision
|-
| upload artifacts || Uploads generated artifacts to a Github Release so they are available to the public. || any kind of artifact || artifacts attached to the release on Github
|-
| prepare || Similar to the `configure system automatically` step, this step will prepare an AUR build environment to build Oolite. || nothing || configured system
|-
| pkgver || Checks the version tag of the local source code and transforms it from semver to an AUR package version number. || working tree || version used by archlinux pacman (package manager) to track installed packages
|-
| package || Generates the AUR package. |||| tarball with files the application needs in a format designed for use by pacman
|-
| publish on AUR || Pushes the AUR package into the AUR repository. || write access on aur package repo for oolite / oolite-git package || shares recipe (PKGBUILD) to build oolite / oolite-git packages on archlinux user systems
|}

{
"builder": "unknown",
"title": "Oolite core",
"version": "1.93.1-190",
"source": "https://github.com/OoliteProject/oolite/releases/tag/1.93.1-190",
"built-at": "2026-07-12T19:59:09+0200",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/",
"expansion_catalog": "https://addons.oolite.space/api/1.0/overview/"
}

Oolite build system

2026-07-12T17:52:57Z

Hiran:

Oolite build system

2026-07-10T14:33:25Z

Hiran:

Oolite build system

2026-07-10T14:28:25Z

Hiran:

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

[[File:Build system.png|frameless|center]]

{| class="wikitable" style="margin:auto"
|-
! Build Step !! Description !! Requires !! Provides
|-
| configure system manually || A developer will maintain his development system will all the required tools and dependencies to build Oolite. Should be supported by scripts. || nothing || configured system
|-
| checkout code || Clone and checkout from the Oolite git repository so it resides in the local filesystem. || configured system || working tree
|-
| change code || A developer will change code in the local filesystem to whatever extent. || working tree || modified working tree
|-
| meson setup || || working tree || meson configuration files
|-
| meson compile || || meson configuration files || compiled and linked output in the build directory
|-
| test/debug manually || A developer will test manually, focusing on the changes he/she applied. || compiled and linked output in the build directory || nothing
|-
| meson test || runs predefined tests || compiled and linked output in the build directory || error log and return status code
|-
| meson install || copies Oolite files to another location on disk || compiled and linked output in the build directory || files in new output location
|-
| meson uninstall || reverse opertion for meson install. Removes the files from the new output location || files in new output location || nothing
|-
| push changes || Push the changes back into the Oolite repository. Likely involves commit and pull request actions. || modified working tree || unmodified working tree
|-
| configure system automatically || Similar to the `configure system manually` step, in CI builds all this has to be scripted. || nothing || configured system
|-
| calculate version number || Generates the checked out version's semver. || working tree ||
|-
| generate tar.gz || Generates an Oolite distribution as tar ball. || compiled and linked output in the build directory || the tar.gz file
|-
| generate AppImage || Generates a Linux AppImage. || the tar.gz file || the AppImage
|-
| generate Flatpak || Generates a Linux Flatpak image. || the tar.gz file || the Flatpak
|-
| generate MSIX || Generates a Windows installer for Oolite using MSIX. || the tar.gz file || the MSIX package
|-
| generate NSIS || Generates a Windows installer for Oolite using NSIS. || the tar.gz file || the executable installer
|-
| tag source code || The CI run will tag the version in the official repository so it is available to all other steps. || the version number || tagged git revision
|-
| upload artifacts || Uploads generated artifacts to a Github Release so they are available to the public. || any kind of artifact || artifacts attached to the release on Github
|-
| prepare || Similar to the `configure system automatically` step, this step will prepare an AUR build environment to build Oolite. || nothing || configured system
|-
| pkgver || Checks the version tag of the local source code and transforms it from semver to an AUR package version number. ||||
|-
| package || Generates the AUR package. ||||
|-
| publish on AUR || Pushes the AUR package into the AUR repository. ||||
|}

-----------------------------

# makepkg starts
#* install prerequisites like clang, meson, jq, ...
#* checkout project
# run prepare() function
#* calculate official version number (semver via gitversion)
# run build() function
#* meson setup
#* meson compile
# run check() function
#* meson test
# run package() function
#* meson install
#* Place custom icon, desktop item for use in menus, custom launcher etc at correct places
# create archlinux package
# makepkg exits
# runtime tests
# publish on AUR

-----------------------------

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option. Although since we updated the dependencies this example should be outdated.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash.These values shall be passed in a JSON file inside the build directory. An example build file can look like this:

{
"title": "Oolite core",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/",
"expansion_catalog": "https://addons.oolite.space/api/1.0/overview/"
}


# build
#* setup/configure
#* compile
#* test unpackaged
#* install <-- why is this here?
# post-build
# packaging
# testing package

Oolite build system

2026-07-10T14:16:38Z

Hiran:

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

[[File:Build system.png|frameless|center]]

{| class="wikitable" style="margin:auto"
|-
! Build Step !! Description !! Requires !! Provides
|-
| configure system manually || A developer will maintain his development system will all the required tools and dependencies to build Oolite. Should be supported by scripts. || nothing || configured system
|-
| checkout code || Clone and checkout from the Oolite git repository so it resides in the local filesystem. ||||
|-
| change code || A developer will change code in the local filesystem to whatever extent. ||||
|-
| meson setup ||||||
|-
| meson compile ||||||
|-
| test/debug manually || A developer will test manually, focusing on the changes he/she applied. ||||
|-
| meson test ||||||
|-
| meson install ||||||
|-
| meson uninstall ||||||
|-
| push changes || Push the changes back into the Oolite repository. Likely involves commit and pull request actions. || || |
|-
| configure system automatically || Similar to the `configure system manually` step, in CI builds all this has to be scripted. || nothing || configured system
|-
| calculate version number || Generates the checked out version's semver. ||||
|-
| generate tar.gz || Generates an Oolite distribution as tar ball. ||||
|-
| generate AppImage || Generates a Linux AppImage. ||||
|-
| generate Flatpak || Generates a Linux Flatpak image. ||||
|-
| generate MSIX || Generates a Windows installer for Oolite using MSIX. ||||
|-
| generate NSIS || Generates a Windows installer for Oolite using NSIS. ||||
|-
| tag source code || The CI run will tag the version in the official repository so it is available to all other steps. ||||
|-
| upload artifacts || Uploads generated artifacts to a Github Release so they are available to the public. ||||
|-
| prepare || Similar to the `configure system automatically` step, this step will prepare an AUR build environment to build Oolite. || nothing || configured system
|-
| pkgver || Checks the version tag of the local source code and transforms it from semver to an AUR package version number. ||||
|-
| package || Generates the AUR package. ||||
|-
| publish on AUR || Pushes the AUR package into the AUR repository. ||||
|}

-----------------------------

# makepkg starts
#* install prerequisites like clang, meson, jq, ...
#* checkout project
# run prepare() function
#* calculate official version number (semver via gitversion)
# run build() function
#* meson setup
#* meson compile
# run check() function
#* meson test
# run package() function
#* meson install
#* Place custom icon, desktop item for use in menus, custom launcher etc at correct places
# create archlinux package
# makepkg exits
# runtime tests
# publish on AUR

-----------------------------

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option. Although since we updated the dependencies this example should be outdated.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash.These values shall be passed in a JSON file inside the build directory. An example build file can look like this:

{
"title": "Oolite core",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/",
"expansion_catalog": "https://addons.oolite.space/api/1.0/overview/"
}


# build
#* setup/configure
#* compile
#* test unpackaged
#* install <-- why is this here?
# post-build
# packaging
# testing package

Oolite build system

2026-07-10T14:15:56Z

Hiran:

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

[[File:Build system.png|frameless|center]]

{| class="wikitable" style="margin:auto"
|-
! Build Step !! Description !! Requires !! Provides
|-
| configure system manually || A developer will maintain his development system will all the required tools and dependencies to build Oolite. Should be supported by scripts. || nothing ||
|-
| checkout code || Clone and checkout from the Oolite git repository so it resides in the local filesystem. ||||
|-
| change code || A developer will change code in the local filesystem to whatever extent. ||||
|-
| meson setup ||||||
|-
| meson compile ||||||
|-
| test/debug manually || A developer will test manually, focusing on the changes he/she applied. ||||
|-
| meson test ||||||
|-
| meson install ||||||
|-
| meson uninstall ||||||
|-
| push changes || Push the changes back into the Oolite repository. Likely involves commit and pull request actions. || || |
|-
| configure system automatically || Similar to the `configure system manually` step, in CI builds all this has to be scripted. || nothing ||
|-
| calculate version number || Generates the checked out version's semver. ||||
|-
| generate tar.gz || Generates an Oolite distribution as tar ball. ||||
|-
| generate AppImage || Generates a Linux AppImage. ||||
|-
| generate Flatpak || Generates a Linux Flatpak image. ||||
|-
| generate MSIX || Generates a Windows installer for Oolite using MSIX. ||||
|-
| generate NSIS || Generates a Windows installer for Oolite using NSIS. ||||
|-
| tag source code || The CI run will tag the version in the official repository so it is available to all other steps. ||||
|-
| upload artifacts || Uploads generated artifacts to a Github Release so they are available to the public. ||||
|-
| prepare || Similar to the `configure system automatically` step, this step will prepare an AUR build environment to build Oolite. || nothing ||
|-
| pkgver || Checks the version tag of the local source code and transforms it from semver to an AUR package version number. ||||
|-
| package || Generates the AUR package. ||||
|-
| publish on AUR || Pushes the AUR package into the AUR repository. ||||
|}

-----------------------------

# makepkg starts
#* install prerequisites like clang, meson, jq, ...
#* checkout project
# run prepare() function
#* calculate official version number (semver via gitversion)
# run build() function
#* meson setup
#* meson compile
# run check() function
#* meson test
# run package() function
#* meson install
#* Place custom icon, desktop item for use in menus, custom launcher etc at correct places
# create archlinux package
# makepkg exits
# runtime tests
# publish on AUR

-----------------------------

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option. Although since we updated the dependencies this example should be outdated.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash.These values shall be passed in a JSON file inside the build directory. An example build file can look like this:

{
"title": "Oolite core",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/",
"expansion_catalog": "https://addons.oolite.space/api/1.0/overview/"
}


# build
#* setup/configure
#* compile
#* test unpackaged
#* install <-- why is this here?
# post-build
# packaging
# testing package

Oolite build system

2026-07-09T07:23:28Z

Hiran:

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

[[File:Build system.png|frameless|center]]

{| class="wikitable" style="margin:auto"
|-
! Build Step !! Description !! Requires !! Provides
|-
| configure system manually || A developer will maintain his development system will all the required tools and dependencies to build Oolite. Should be supported by scripts. ||||
|-
| checkout code || Clone and checkout from the Oolite git repository so it resides in the local filesystem. ||||
|-
| change code || A developer will change code in the local filesystem to whatever extent. ||||
|-
| meson setup ||||||
|-
| meson compile ||||||
|-
| test/debug manually || A developer will test manually, focusing on the changes he/she applied. ||||
|-
| meson test ||||||
|-
| meson install ||||||
|-
| meson uninstall ||||||
|-
| push changes || Push the changes back into the Oolite repository. Likely involves commit and pull request actions. || || |
|-
| configure system automatically || Similar to the `configure system manually` step, in CI builds all this has to be scripted. ||||
|-
| calculate version number || Generates the checked out version's semver. ||||
|-
| generate tar.gz || Generates an Oolite distribution as tar ball. ||||
|-
| generate AppImage || Generates a Linux AppImage. ||||
|-
| generate Flatpak || Generates a Linux Flatpak image. ||||
|-
| generate MSIX || Generates a Windows installer for Oolite using MSIX. ||||
|-
| generate NSIS || Generates a Windows installer for Oolite using NSIS. ||||
|-
| tag source code || The CI run will tag the version in the official repository so it is available to all other steps. ||||
|-
| upload artifacts || Uploads generated artifacts to a Github Release so they are available to the public. ||||
|-
| prepare || Similar to the `configure system automatically` step, this step will prepare an AUR build environment to build Oolite. ||||
|-
| pkgver || Checks the version tag of the local source code and transforms it from semver to an AUR package version number. ||||
|-
| package || Generates the AUR package. ||||
|-
| publish on AUR || Pushes the AUR package into the AUR repository. ||||
|}

-----------------------------

# makepkg starts
#* install prerequisites like clang, meson, jq, ...
#* checkout project
# run prepare() function
#* calculate official version number (semver via gitversion)
# run build() function
#* meson setup
#* meson compile
# run check() function
#* meson test
# run package() function
#* meson install
#* Place custom icon, desktop item for use in menus, custom launcher etc at correct places
# create archlinux package
# makepkg exits
# runtime tests
# publish on AUR

-----------------------------

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option. Although since we updated the dependencies this example should be outdated.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash.These values shall be passed in a JSON file inside the build directory. An example build file can look like this:

{
"title": "Oolite core",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/",
"expansion_catalog": "https://addons.oolite.space/api/1.0/overview/"
}


# build
#* setup/configure
#* compile
#* test unpackaged
#* install <-- why is this here?
# post-build
# packaging
# testing package

Oolite build system

2026-07-09T07:17:44Z

Hiran:

Oolite build system

2026-07-09T07:12:13Z

Hiran:

Oolite build system

2026-07-09T07:10:17Z

Hiran:

Oolite build system

2026-07-09T07:04:39Z

Hiran:

Developer's Corner

2026-07-09T07:02:53Z

Hiran:

Oolite build system

2026-07-09T07:02:08Z

Hiran: Hiran moved page The build system to Oolite build system

The build system

2026-07-09T07:02:08Z

Hiran: Hiran moved page The build system to Oolite build system

#REDIRECT [[Oolite build system]]

Oolite build system

2026-07-09T06:30:02Z

Hiran:

Oolite build system

2026-07-09T06:29:27Z

Hiran:

Oolite build system

2026-07-09T06:24:20Z

Hiran:

Oolite build system

2026-07-09T06:18:02Z

Hiran:

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

[[File:Build system.png|frameless|center]]

# makepkg starts
#* install prerequisites like clang, meson, jq, ...
#* checkout project
# run prepare() function
#* calculate official version number (semver via gitversion)
# run build() function
#* meson setup
#* meson compile
# run check() function
#* meson test
# run package() function
#* meson install
#* Place custom icon, desktop item for use in menus, custom launcher etc at correct places
# create archlinux package
# makepkg exits
# runtime tests
# publish on AUR

-----------------------------

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option. Although since we updated the dependencies this example should be outdated.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash.These values shall be passed in a JSON file inside the build directory. An example build file can look like this:

{
"title": "Oolite core",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/",
"expansion_catalog": "https://addons.oolite.space/api/1.0/overview/"
}


# build
#* setup/configure
#* compile
#* test unpackaged
#* install <-- why is this here?
# post-build
# packaging
# testing package

File:Build system old.png

2026-07-09T06:14:19Z

Hiran: PlantUML diagram for the build process for developers, CI and AUR distro packagers

== Summary ==
PlantUML diagram for the build process for developers, CI and AUR distro packagers

Oolite build system

2026-07-09T06:12:19Z

Hiran:

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

# makepkg starts
#* install prerequisites like clang, meson, jq, ...
#* checkout project
# run prepare() function
#* calculate official version number (semver via gitversion)
# run build() function
#* meson setup
#* meson compile
# run check() function
#* meson test
# run package() function
#* meson install
#* Place custom icon, desktop item for use in menus, custom launcher etc at correct places
# create archlinux package
# makepkg exits
# runtime tests
# publish on AUR

-----------------------------

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option. Although since we updated the dependencies this example should be outdated.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash.These values shall be passed in a JSON file inside the build directory. An example build file can look like this:

{
"title": "Oolite core",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/",
"expansion_catalog": "https://addons.oolite.space/api/1.0/overview/"
}


# build
#* setup/configure
#* compile
#* test unpackaged
#* install <-- why is this here?
# post-build
# packaging
# testing package

Oolite build system

2026-07-09T06:12:00Z

Hiran: Created page with "= The build system (architecture) = Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes] # makepkg..."

= The build system (architecture) =

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

# makepkg starts
#* install prerequisites like clang, meson, jq, ...
#* checkout project
# run prepare() function
#* calculate official version number (semver via gitversion)
# run build() function
#* meson setup
#* meson compile
# run check() function
#* meson test
# run package() function
#* meson install
#* Place custom icon, desktop item for use in menus, custom launcher etc at correct places
# create archlinux package
# makepkg exits
# runtime tests
# publish on AUR

-----------------------------

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option. Although since we updated the dependencies this example should be outdated.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash.These values shall be passed in a JSON file inside the build directory. An example build file can look like this:

{
"title": "Oolite core",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/",
"expansion_catalog": "https://addons.oolite.space/api/1.0/overview/"
}


# build
#* setup/configure
#* compile
#* test unpackaged
#* install <-- why is this here?
# post-build
# packaging
# testing package

Developer's Corner

2026-07-09T06:10:00Z

Hiran:

Developer's Corner

2026-07-03T16:59:21Z

Hiran: /* The build system (architecture) */

Here you will find information that helps understanding the Oolite source code, build and test the project.

* [[Contributing to the project]]
* [[Release Process]]
* [[Branding]], [[Branding History]]
* [https://ooliteproject.github.io/oolite/ Oolite API documentation]
* [https://ooliteproject.github.io/oolite/ Doxygen Documentation]
* [https://ooliteproject.github.io/oolite/coverage/index.html Code Coverage Report]
* [[Cross Platform IDEs]]
* [[Compiling with Clang instead of gcc]] (Windows/Linux)

== The build system (architecture) ==

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

# makepkg starts
#* install prerequisites like clang, meson, jq, ...
#* checkout project
# run prepare() function
#* calculate official version number (semver via gitversion)
# run build() function
#* meson setup
#* meson compile
# run check() function
#* meson test
# run package() function
#* meson install
#* Place custom icon, desktop item for use in menus, custom launcher etc at correct places
# create archlinux package
# makepkg exits
# runtime tests
# publish on AUR

-----------------------------

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option. Although since we updated the dependencies this example should be outdated.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash.These values shall be passed in a JSON file inside the build directory. An example build file can look like this:

{
"title": "Oolite core",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/",
"expansion_catalog": "https://addons.oolite.space/api/1.0/overview/"
}


# build
#* setup/configure
#* compile
#* test unpackaged
#* install <-- why is this here?
# post-build
# packaging
# testing package

== OS Specific parts ==

{| class="wikitable" style="margin:auto"
|+ Operating System dependent stuff
|-
! Procedure !! Apple Mac !! Linux !! Windows
|-
| Setting up a development environment || [[Development on Apple Mac]], [[Cross Platform IDEs]] || [[Development on Linux]], [[Cross Platform IDEs]] || [[Development on Windows]], [[Cross Platform IDEs]]
|-
| Compiling || [[Compiling on Apple Mac]] || [[Compiling on Linux]] || [[Developing Oolite#On_Windows_2 | Compiling on Windows]]
|-
| Testing || [[Testing on Apple Mac]], [[Common Testing]] || [[Testing on Linux]], [[Common Testing]] || [[Testing on Windows]], [[Common Testing]]
|-
| Packaging into Installer || [[Installer on Apple Mac]] || [[Installer on Linux]] || [[Installer on Windows]]
|-
| Running || [[Running Oolite-Mac]] || ||
|}

==Releasing the code==

Once you developed a while you might no longer be happy that all you have created is called 'nightly' or 'prerelease' or 'unstable'.

If you are convinced the current status should be published as 'stable' or 'release', follow the [[Oolite Release Process]].

[[Category:Oolite Development]]

== Hints ==

The code is organized across several git repositories. The main one refers to the others as submodules - but always to a concise commit.

If you need to update submodules you also need to tell people to update the reference in the main repository. Here you can see that handling submodules can lead to strange effects: https://bb.oolite.space/viewtopic.php?f=3&t=21470

To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules

Developer's Corner

2026-06-30T17:02:51Z

Hiran: /* The build system (architecture) */

Here you will find information that helps understanding the Oolite source code, build and test the project.

* [[Contributing to the project]]
* [[Release Process]]
* [[Branding]], [[Branding History]]
* [https://ooliteproject.github.io/oolite/ Oolite API documentation]
* [https://ooliteproject.github.io/oolite/ Doxygen Documentation]
* [https://ooliteproject.github.io/oolite/coverage/index.html Code Coverage Report]
* [[Cross Platform IDEs]]
* [[Compiling with Clang instead of gcc]] (Windows/Linux)

== The build system (architecture) ==

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option. Although since we updated the dependencies this example should be outdated.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash.These values shall be passed in a JSON file inside the build directory. An example build file can look like this:

{
"title": "Oolite core",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/",
"expansion_catalog": "https://addons.oolite.space/api/1.0/overview/"
}


# build
#* setup/configure
#* compile
#* test unpackaged
#* install <-- why is this here?
# post-build
# packaging
# testing package

== OS Specific parts ==

{| class="wikitable" style="margin:auto"
|+ Operating System dependent stuff
|-
! Procedure !! Apple Mac !! Linux !! Windows
|-
| Setting up a development environment || [[Development on Apple Mac]], [[Cross Platform IDEs]] || [[Development on Linux]], [[Cross Platform IDEs]] || [[Development on Windows]], [[Cross Platform IDEs]]
|-
| Compiling || [[Compiling on Apple Mac]] || [[Compiling on Linux]] || [[Developing Oolite#On_Windows_2 | Compiling on Windows]]
|-
| Testing || [[Testing on Apple Mac]], [[Common Testing]] || [[Testing on Linux]], [[Common Testing]] || [[Testing on Windows]], [[Common Testing]]
|-
| Packaging into Installer || [[Installer on Apple Mac]] || [[Installer on Linux]] || [[Installer on Windows]]
|-
| Running || [[Running Oolite-Mac]] || ||
|}

==Releasing the code==

Once you developed a while you might no longer be happy that all you have created is called 'nightly' or 'prerelease' or 'unstable'.

If you are convinced the current status should be published as 'stable' or 'release', follow the [[Oolite Release Process]].

[[Category:Oolite Development]]

== Hints ==

The code is organized across several git repositories. The main one refers to the others as submodules - but always to a concise commit.

If you need to update submodules you also need to tell people to update the reference in the main repository. Here you can see that handling submodules can lead to strange effects: https://bb.oolite.space/viewtopic.php?f=3&t=21470

To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules

Developer's Corner

2026-06-30T16:54:13Z

Hiran: /* The build system (architecture) */

Here you will find information that helps understanding the Oolite source code, build and test the project.

* [[Contributing to the project]]
* [[Release Process]]
* [[Branding]], [[Branding History]]
* [https://ooliteproject.github.io/oolite/ Oolite API documentation]
* [https://ooliteproject.github.io/oolite/ Doxygen Documentation]
* [https://ooliteproject.github.io/oolite/coverage/index.html Code Coverage Report]
* [[Cross Platform IDEs]]
* [[Compiling with Clang instead of gcc]] (Windows/Linux)

== The build system (architecture) ==

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option. Although since we updated the dependencies this example should be outdated.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash.These values shall be passed in a JSON file inside the build directory. An example build file can look like this:

{
"title": "Oolite core",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/"
}


# build
#* setup/configure
#* compile
#* test unpackaged
#* install <-- why is this here?
# post-build
# packaging
# testing package

== OS Specific parts ==

{| class="wikitable" style="margin:auto"
|+ Operating System dependent stuff
|-
! Procedure !! Apple Mac !! Linux !! Windows
|-
| Setting up a development environment || [[Development on Apple Mac]], [[Cross Platform IDEs]] || [[Development on Linux]], [[Cross Platform IDEs]] || [[Development on Windows]], [[Cross Platform IDEs]]
|-
| Compiling || [[Compiling on Apple Mac]] || [[Compiling on Linux]] || [[Developing Oolite#On_Windows_2 | Compiling on Windows]]
|-
| Testing || [[Testing on Apple Mac]], [[Common Testing]] || [[Testing on Linux]], [[Common Testing]] || [[Testing on Windows]], [[Common Testing]]
|-
| Packaging into Installer || [[Installer on Apple Mac]] || [[Installer on Linux]] || [[Installer on Windows]]
|-
| Running || [[Running Oolite-Mac]] || ||
|}

==Releasing the code==

Once you developed a while you might no longer be happy that all you have created is called 'nightly' or 'prerelease' or 'unstable'.

If you are convinced the current status should be published as 'stable' or 'release', follow the [[Oolite Release Process]].

[[Category:Oolite Development]]

== Hints ==

The code is organized across several git repositories. The main one refers to the others as submodules - but always to a concise commit.

If you need to update submodules you also need to tell people to update the reference in the main repository. Here you can see that handling submodules can lead to strange effects: https://bb.oolite.space/viewtopic.php?f=3&t=21470

To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules

Developer's Corner

2026-06-28T17:40:30Z

Hiran: /* The build system (architecture) */

Here you will find information that helps understanding the Oolite source code, build and test the project.

* [[Contributing to the project]]
* [[Release Process]]
* [[Branding]], [[Branding History]]
* [https://ooliteproject.github.io/oolite/ Oolite API documentation]
* [https://ooliteproject.github.io/oolite/ Doxygen Documentation]
* [https://ooliteproject.github.io/oolite/coverage/index.html Code Coverage Report]
* [[Cross Platform IDEs]]
* [[Compiling with Clang instead of gcc]] (Windows/Linux)

== The build system (architecture) ==

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option. Although since we updated the dependencies this example should be outdated.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash.These values shall be passed in a JSON file inside the build directory. An example build file can look like this:

{
"title": "Oolite core",
"identifier": "org.oolite.oolite",
"required_oolite_version": "1.93",
"license": "GPL 2+ / CC-BY-NC-SA 3.0 - see LICENSE.md for details",
"author": "Giles Williams, Jens Ayton and contributors",
"information_url": "https://oolite.space/"
}


# build
# testing unpackaged
# post-build
# packaging
# testing package

== OS Specific parts ==

{| class="wikitable" style="margin:auto"
|+ Operating System dependent stuff
|-
! Procedure !! Apple Mac !! Linux !! Windows
|-
| Setting up a development environment || [[Development on Apple Mac]], [[Cross Platform IDEs]] || [[Development on Linux]], [[Cross Platform IDEs]] || [[Development on Windows]], [[Cross Platform IDEs]]
|-
| Compiling || [[Compiling on Apple Mac]] || [[Compiling on Linux]] || [[Developing Oolite#On_Windows_2 | Compiling on Windows]]
|-
| Testing || [[Testing on Apple Mac]], [[Common Testing]] || [[Testing on Linux]], [[Common Testing]] || [[Testing on Windows]], [[Common Testing]]
|-
| Packaging into Installer || [[Installer on Apple Mac]] || [[Installer on Linux]] || [[Installer on Windows]]
|-
| Running || [[Running Oolite-Mac]] || ||
|}

==Releasing the code==

Once you developed a while you might no longer be happy that all you have created is called 'nightly' or 'prerelease' or 'unstable'.

If you are convinced the current status should be published as 'stable' or 'release', follow the [[Oolite Release Process]].

[[Category:Oolite Development]]

== Hints ==

The code is organized across several git repositories. The main one refers to the others as submodules - but always to a concise commit.

If you need to update submodules you also need to tell people to update the reference in the main repository. Here you can see that handling submodules can lead to strange effects: https://bb.oolite.space/viewtopic.php?f=3&t=21470

To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules

Developer's Corner

2026-06-27T16:45:28Z

Hiran: /* The build system (architecture) */

Here you will find information that helps understanding the Oolite source code, build and test the project.

* [[Contributing to the project]]
* [[Release Process]]
* [[Branding]], [[Branding History]]
* [https://ooliteproject.github.io/oolite/ Oolite API documentation]
* [https://ooliteproject.github.io/oolite/ Doxygen Documentation]
* [https://ooliteproject.github.io/oolite/coverage/index.html Code Coverage Report]
* [[Cross Platform IDEs]]
* [[Compiling with Clang instead of gcc]] (Windows/Linux)

== The build system (architecture) ==

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash
# build
# testing unpackaged
# post-build
# packaging
# testing package

== OS Specific parts ==

{| class="wikitable" style="margin:auto"
|+ Operating System dependent stuff
|-
! Procedure !! Apple Mac !! Linux !! Windows
|-
| Setting up a development environment || [[Development on Apple Mac]], [[Cross Platform IDEs]] || [[Development on Linux]], [[Cross Platform IDEs]] || [[Development on Windows]], [[Cross Platform IDEs]]
|-
| Compiling || [[Compiling on Apple Mac]] || [[Compiling on Linux]] || [[Developing Oolite#On_Windows_2 | Compiling on Windows]]
|-
| Testing || [[Testing on Apple Mac]], [[Common Testing]] || [[Testing on Linux]], [[Common Testing]] || [[Testing on Windows]], [[Common Testing]]
|-
| Packaging into Installer || [[Installer on Apple Mac]] || [[Installer on Linux]] || [[Installer on Windows]]
|-
| Running || [[Running Oolite-Mac]] || ||
|}

==Releasing the code==

Once you developed a while you might no longer be happy that all you have created is called 'nightly' or 'prerelease' or 'unstable'.

If you are convinced the current status should be published as 'stable' or 'release', follow the [[Oolite Release Process]].

[[Category:Oolite Development]]

== Hints ==

The code is organized across several git repositories. The main one refers to the others as submodules - but always to a concise commit.

If you need to update submodules you also need to tell people to update the reference in the main repository. Here you can see that handling submodules can lead to strange effects: https://bb.oolite.space/viewtopic.php?f=3&t=21470

To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules

Developer's Corner

2026-06-27T16:40:22Z

Hiran: /* The build system (architecture) */

Here you will find information that helps understanding the Oolite source code, build and test the project.

* [[Contributing to the project]]
* [[Release Process]]
* [[Branding]], [[Branding History]]
* [https://ooliteproject.github.io/oolite/ Oolite API documentation]
* [https://ooliteproject.github.io/oolite/ Doxygen Documentation]
* [https://ooliteproject.github.io/oolite/coverage/index.html Code Coverage Report]
* [[Cross Platform IDEs]]
* [[Compiling with Clang instead of gcc]] (Windows/Linux)

== The build system (architecture) ==

Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]

# pre-build
#* Iniialise a clean minimal build enviornmnetMany issues during or after build are due to having uncessary things being present. Whether this is done through a clean chroot, docker container, VPS, github/gitlab workflow, Virtual machine etc is an implementation detail.
#* download sourcecodeThis should include oolite sourcecode as well as the code needed for external dependencies.
#* install required dependenciesThe baseline discussed at viewtopic.php?p=304440 should make this part a lot easier./p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.objc2 can only be built by clang, requires gnustep base and make to be built with clang. Also no released versions of gnustep tools support latest clang release (fixes are avaiiable). Targets that use the gcc provided libobjc don't have this need.
#* changes to sourcecode to allow succesfull buildsexample : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option.
#* set/update values that can not be determined before build time.This includes things like sourcecode url, build environment, git commit hash
# build
# testing unpackaged
# post-build
# packaging
# testing package

== OS Specific parts ==

{| class="wikitable" style="margin:auto"
|+ Operating System dependent stuff
|-
! Procedure !! Apple Mac !! Linux !! Windows
|-
| Setting up a development environment || [[Development on Apple Mac]], [[Cross Platform IDEs]] || [[Development on Linux]], [[Cross Platform IDEs]] || [[Development on Windows]], [[Cross Platform IDEs]]
|-
| Compiling || [[Compiling on Apple Mac]] || [[Compiling on Linux]] || [[Developing Oolite#On_Windows_2 | Compiling on Windows]]
|-
| Testing || [[Testing on Apple Mac]], [[Common Testing]] || [[Testing on Linux]], [[Common Testing]] || [[Testing on Windows]], [[Common Testing]]
|-
| Packaging into Installer || [[Installer on Apple Mac]] || [[Installer on Linux]] || [[Installer on Windows]]
|-
| Running || [[Running Oolite-Mac]] || ||
|}

==Releasing the code==

Once you developed a while you might no longer be happy that all you have created is called 'nightly' or 'prerelease' or 'unstable'.

If you are convinced the current status should be published as 'stable' or 'release', follow the [[Oolite Release Process]].

[[Category:Oolite Development]]

== Hints ==

The code is organized across several git repositories. The main one refers to the others as submodules - but always to a concise commit.

If you need to update submodules you also need to tell people to update the reference in the main repository. Here you can see that handling submodules can lead to strange effects: https://bb.oolite.space/viewtopic.php?f=3&t=21470

To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules

Developer's Corner

2026-06-26T13:08:28Z

Hiran:

Common Testing

2026-06-06T09:49:33Z

Hiran:

[[File:FPS report.png|right|400px]]
Here are some tests that can be performed regardless of the operating system.

== Audio output ==

Run Oolite and check whether this output works as intended:
* Background noise
* Flying/shooting
* Voice output

== Performance Test ==

The main functionality in Oolite is to process the "game loop". This reads user input, processes the world including running all your OXP/OXZs, and then renders out the world view. For meaningful tests you need to have a repeatable base. A good metric for performance is the number of [[Frame rate|frames per second]] (FPS) that Oolite can process.

If you want to check performance, you must check with FPS uncapped, otherwise you are always getting v-sync FPS, which is usually a low number like 60 for a 60Hz monitor, 144 for a 144Hz one ''etc''.

Add the '''"animation_timer_interval" = x;''' in your OoliteDefaults.plist, where x is 1.0/Maximum FPS You Want To Achieve. I usually set it to 0.001 which tells Oolite to "go for 1000 FPS if you can". Then you can compare actual performance between builds.

Also, disable v-sync to have uncapped FPS. You do this by setting the OoliteDefaults.plist key '''"v-sync" = NO;'''.

When comparing the performance of builds, always check with more or less the same number of entities in the system. If in one case you get 250 entities and in the other you get 70, then results may be biased (it takes much more processing power to manage the 250). Try to compare instances where the two system entity numbers are as close as possible. Shift+F shows you this info in the Oolite "Test Release" builds. Phkb wrote an expansion for that: [https://app.box.com/s/xrkkr5ylizshjng2dpc8uu9q6b39zt49 CustomPopulator.oxp.zip]. And as other OXP/OXZs may inhibit the build performance, make sure this is the only one you are running on top of a [[Vanilla game]].

After starting Oolite, press Shift-F to show the frame rate on the screen, then fly around.

=== Example ===

Here in ASCII Plist format:

{
"Jameson-humbletrash" = "-29624";
"animation_timer_interval" = "0.001";
"debug-settings-override" = {
};
"gamma-value" = 1;
"v-sync" = no;
"volume_control" = "0.5";
"window_height" = 1043;
"window_width" = 1920;
}

Or the same as XML:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//GNUstep//DTD plist 0.9//EN" "http://www.gnustep.org/plist-0_9.xml">
<plist version="0.9">
<dict>
<key>NSGlobalDomain</key>
<dict>
</dict>
<key>oolite</key>
<dict>
<key>Jameson-humbletrash</key>
<integer>-29624</integer>
<key>animation_timer_interval</key>
<real>0.001</real>
<key>gamma-value</key>
<real>1</real>
<key>v-sync</key>
<false/>
<key>volume_control</key>
<real>0.5</real>
<key>window_height</key>
<integer>1043</integer>
<key>window_width</key>
<integer>1920</integer>
</dict>
</dict>
</plist>

=== Note ===
More of the configuration file's settings are documented on the [[Hidden Settings in Oolite]] wiki page.

== Comparison ==

Now we need to compare several such tests in order to see patterns. To facilitate this and also communicate to others, start filling in a table like this:

{| class="wikitable" style="margin:auto"
|+ Caption text
|-
! Oolite Version/Build/package !! Installed expansions !! Amount of entities !! screen/window size !! perceived FPS
|-
| 1.90/debug/.run || CustomPopulator || 360 || 800x600 || 70
|-
| 1.92/test/appimage || CustomPopulator || 358 || 1024x768 || 35
|-
| 1.93/flatpak/release || CustomPopulator || 360 || 1233x700 || 40
|}

== Links ==
*[[Frame rate]]
*[[Developer's Corner]]
*[[User:Hiran|Hiran]]

Branding

2026-06-02T18:28:42Z

Hiran: /* Others */

This page intends to describe where to find icons and other material, how to use them and in case of icon change lists all the places that need an update.
Information is based on the discussion in the [https://bb.oolite.space/viewtopic.php?t=21464&start=180 forum thread].

= Icon Change =

Currently this is just a list of locations we need to check. This may be enhanced by procedures to actually perform the changes.

== Oolite ==

* oolite\debian\oolite-logo1.xpm
* oolite\Doc\OoliteRS.odt
* oolite\Documentation\docs\assets\oolite-logo.png
* oolite\installers\win32\OoliteInstallerHeaderBitmap_ModernUI.bmp
* oolite\installers\win32\Oolite.ico
* oolite\installers\win32\Oolite-HDR.ico
* oolite\installers\win32\OoliteInstallerFinishpageBitmap.bmp
* oolite\Resources\Images\splash@2x.png
* oolite\Resources\Images\WMicon.bmp
* oolite\Resources\Images\splash.bmp
* oolite\Resources\Images\splash.png

== Debug Console ==

* oolite-debug-console\images\OoJSC.icns
* oolite-debug-console\images\OoJSC.ico
* oolite-debug-console\images\OoJSC16x16.png
* oolite-debug-console\images\OoJSC24x24.png
* oolite-debug-console\images\OoJSC32x32.png
* oolite-debug-console\images\OoJSC48x48.png
* oolite-debug-console\images\OoJSC64x64.png
* oolite-debug-console\images\OoJSC96x96.png
* oolite-debug-console\images\OoJSC128x128.png
* oolite-debug-console\images\OoJSC192x192.png
* oolite-debug-console\images\OoJSC256x256.png

== Oolite Starter ==

* OoliteStarter/src/main/resources/icons/32px-Oolite-oxp-icon.png
* OoliteStarter/src/main/resources/icons/OoliteIcon24.png
* OoliteStarter/src/main/resources/images/Mr_Gimlet_Oolite.png
* OoliteStarter/src/main/resources/oolite_logo.ico
* OoliteStarter/src/main/resources/oolite_logo.png

== Wiki ==
* the logo on the wiki (top left of every page)
* the logo on the wiki (gray icon on the main page)
* the logo on the wiki (colored icon on the main oolite page)
* the favicon on the wiki

== Others ==

* the logo on oolite.space (updates to the only-static and only-media branches in oolite-web)
* the favicon on oolite.space
* the logo on bb.oolite.space
* the favicon on bb.oolite.space
* the logo in the Microsoft Store
* the logo in the FlatHub
* Is there a central repository for AppImages? If so, there.
* the logo on the GitHub site.OoliteStarter/

= Related =

See also [[Branding History]]

Branding

2026-05-31T09:51:17Z

Hiran: /* Oolite Starter */

This page intends to describe where to find icons and other material, how to use them and in case of icon change lists all the places that need an update.
Information is based on the discussion in the [https://bb.oolite.space/viewtopic.php?t=21464&start=180 forum thread].

= Icon Change =

Currently this is just a list of locations we need to check. This may be enhanced by procedures to actually perform the changes.

== Oolite ==

* oolite\debian\oolite-logo1.xpm
* oolite\Doc\OoliteRS.odt
* oolite\Documentation\docs\assets\oolite-logo.png
* oolite\installers\win32\OoliteInstallerHeaderBitmap_ModernUI.bmp
* oolite\installers\win32\Oolite.ico
* oolite\installers\win32\Oolite-HDR.ico
* oolite\installers\win32\OoliteInstallerFinishpageBitmap.bmp
* oolite\Resources\Images\splash@2x.png
* oolite\Resources\Images\WMicon.bmp
* oolite\Resources\Images\splash.bmp
* oolite\Resources\Images\splash.png

== Debug Console ==

* oolite-debug-console\images\OoJSC.icns
* oolite-debug-console\images\OoJSC.ico
* oolite-debug-console\images\OoJSC16x16.png
* oolite-debug-console\images\OoJSC24x24.png
* oolite-debug-console\images\OoJSC32x32.png
* oolite-debug-console\images\OoJSC48x48.png
* oolite-debug-console\images\OoJSC64x64.png
* oolite-debug-console\images\OoJSC96x96.png
* oolite-debug-console\images\OoJSC128x128.png
* oolite-debug-console\images\OoJSC192x192.png
* oolite-debug-console\images\OoJSC256x256.png

== Oolite Starter ==

* OoliteStarter/src/main/resources/icons/32px-Oolite-oxp-icon.png
* OoliteStarter/src/main/resources/icons/OoliteIcon24.png
* OoliteStarter/src/main/resources/images/Mr_Gimlet_Oolite.png
* OoliteStarter/src/main/resources/oolite_logo.ico
* OoliteStarter/src/main/resources/oolite_logo.png

== Others ==

* the logo on oolite.space (updates to the only-static and only-media branches in oolite-web)
* the favicon on oolite.space
* the logo on bb.oolite.space
* the favicon on bb.oolite.space
* the logo in the Microsoft Store
* the logo in the FlatHub
* Is there a central repository for AppImages? If so, there.
* the logo on the GitHub site.OoliteStarter/
* the logo on the wiki
* the favicon on the wiki

= Related =

See also [[Branding History]]

Branding

2026-05-31T09:51:09Z

Hiran: /* Debug Console */

This page intends to describe where to find icons and other material, how to use them and in case of icon change lists all the places that need an update.
Information is based on the discussion in the [https://bb.oolite.space/viewtopic.php?t=21464&start=180 forum thread].

= Icon Change =

Currently this is just a list of locations we need to check. This may be enhanced by procedures to actually perform the changes.

== Oolite ==

* oolite\debian\oolite-logo1.xpm
* oolite\Doc\OoliteRS.odt
* oolite\Documentation\docs\assets\oolite-logo.png
* oolite\installers\win32\OoliteInstallerHeaderBitmap_ModernUI.bmp
* oolite\installers\win32\Oolite.ico
* oolite\installers\win32\Oolite-HDR.ico
* oolite\installers\win32\OoliteInstallerFinishpageBitmap.bmp
* oolite\Resources\Images\splash@2x.png
* oolite\Resources\Images\WMicon.bmp
* oolite\Resources\Images\splash.bmp
* oolite\Resources\Images\splash.png

== Debug Console ==

* oolite-debug-console\images\OoJSC.icns
* oolite-debug-console\images\OoJSC.ico
* oolite-debug-console\images\OoJSC16x16.png
* oolite-debug-console\images\OoJSC24x24.png
* oolite-debug-console\images\OoJSC32x32.png
* oolite-debug-console\images\OoJSC48x48.png
* oolite-debug-console\images\OoJSC64x64.png
* oolite-debug-console\images\OoJSC96x96.png
* oolite-debug-console\images\OoJSC128x128.png
* oolite-debug-console\images\OoJSC192x192.png
* oolite-debug-console\images\OoJSC256x256.png

== Oolite Starter ==

OoliteStarter/src/main/resources/icons/32px-Oolite-oxp-icon.png
OoliteStarter/src/main/resources/icons/OoliteIcon24.png
OoliteStarter/src/main/resources/images/Mr_Gimlet_Oolite.png
OoliteStarter/src/main/resources/oolite_logo.ico
OoliteStarter/src/main/resources/oolite_logo.png

== Others ==

* the logo on oolite.space (updates to the only-static and only-media branches in oolite-web)
* the favicon on oolite.space
* the logo on bb.oolite.space
* the favicon on bb.oolite.space
* the logo in the Microsoft Store
* the logo in the FlatHub
* Is there a central repository for AppImages? If so, there.
* the logo on the GitHub site.OoliteStarter/
* the logo on the wiki
* the favicon on the wiki

= Related =

See also [[Branding History]]

Branding

2026-05-31T09:50:56Z

Hiran: /* Oolite */

This page intends to describe where to find icons and other material, how to use them and in case of icon change lists all the places that need an update.
Information is based on the discussion in the [https://bb.oolite.space/viewtopic.php?t=21464&start=180 forum thread].

= Icon Change =

Currently this is just a list of locations we need to check. This may be enhanced by procedures to actually perform the changes.

== Oolite ==

* oolite\debian\oolite-logo1.xpm
* oolite\Doc\OoliteRS.odt
* oolite\Documentation\docs\assets\oolite-logo.png
* oolite\installers\win32\OoliteInstallerHeaderBitmap_ModernUI.bmp
* oolite\installers\win32\Oolite.ico
* oolite\installers\win32\Oolite-HDR.ico
* oolite\installers\win32\OoliteInstallerFinishpageBitmap.bmp
* oolite\Resources\Images\splash@2x.png
* oolite\Resources\Images\WMicon.bmp
* oolite\Resources\Images\splash.bmp
* oolite\Resources\Images\splash.png

== Debug Console ==

oolite-debug-console\images\OoJSC.icns
oolite-debug-console\images\OoJSC.ico
oolite-debug-console\images\OoJSC16x16.png
oolite-debug-console\images\OoJSC24x24.png
oolite-debug-console\images\OoJSC32x32.png
oolite-debug-console\images\OoJSC48x48.png
oolite-debug-console\images\OoJSC64x64.png
oolite-debug-console\images\OoJSC96x96.png
oolite-debug-console\images\OoJSC128x128.png
oolite-debug-console\images\OoJSC192x192.png
oolite-debug-console\images\OoJSC256x256.png

== Oolite Starter ==

OoliteStarter/src/main/resources/icons/32px-Oolite-oxp-icon.png
OoliteStarter/src/main/resources/icons/OoliteIcon24.png
OoliteStarter/src/main/resources/images/Mr_Gimlet_Oolite.png
OoliteStarter/src/main/resources/oolite_logo.ico
OoliteStarter/src/main/resources/oolite_logo.png

== Others ==

* the logo on oolite.space (updates to the only-static and only-media branches in oolite-web)
* the favicon on oolite.space
* the logo on bb.oolite.space
* the favicon on bb.oolite.space
* the logo in the Microsoft Store
* the logo in the FlatHub
* Is there a central repository for AppImages? If so, there.
* the logo on the GitHub site.OoliteStarter/
* the logo on the wiki
* the favicon on the wiki

= Related =

See also [[Branding History]]

Branding

2026-05-31T09:50:35Z

Hiran: /* Others */

This page intends to describe where to find icons and other material, how to use them and in case of icon change lists all the places that need an update.
Information is based on the discussion in the [https://bb.oolite.space/viewtopic.php?t=21464&start=180 forum thread].

= Icon Change =

Currently this is just a list of locations we need to check. This may be enhanced by procedures to actually perform the changes.

== Oolite ==

oolite\debian\oolite-logo1.xpm
oolite\Doc\OoliteRS.odt
oolite\Documentation\docs\assets\oolite-logo.png
oolite\installers\win32\OoliteInstallerHeaderBitmap_ModernUI.bmp
oolite\installers\win32\Oolite.ico
oolite\installers\win32\Oolite-HDR.ico
oolite\installers\win32\OoliteInstallerFinishpageBitmap.bmp
oolite\Resources\Images\splash@2x.png
oolite\Resources\Images\WMicon.bmp
oolite\Resources\Images\splash.bmp
oolite\Resources\Images\splash.png

== Debug Console ==

oolite-debug-console\images\OoJSC.icns
oolite-debug-console\images\OoJSC.ico
oolite-debug-console\images\OoJSC16x16.png
oolite-debug-console\images\OoJSC24x24.png
oolite-debug-console\images\OoJSC32x32.png
oolite-debug-console\images\OoJSC48x48.png
oolite-debug-console\images\OoJSC64x64.png
oolite-debug-console\images\OoJSC96x96.png
oolite-debug-console\images\OoJSC128x128.png
oolite-debug-console\images\OoJSC192x192.png
oolite-debug-console\images\OoJSC256x256.png

== Oolite Starter ==

OoliteStarter/src/main/resources/icons/32px-Oolite-oxp-icon.png
OoliteStarter/src/main/resources/icons/OoliteIcon24.png
OoliteStarter/src/main/resources/images/Mr_Gimlet_Oolite.png
OoliteStarter/src/main/resources/oolite_logo.ico
OoliteStarter/src/main/resources/oolite_logo.png

== Others ==

* the logo on oolite.space (updates to the only-static and only-media branches in oolite-web)
* the favicon on oolite.space
* the logo on bb.oolite.space
* the favicon on bb.oolite.space
* the logo in the Microsoft Store
* the logo in the FlatHub
* Is there a central repository for AppImages? If so, there.
* the logo on the GitHub site.OoliteStarter/
* the logo on the wiki
* the favicon on the wiki

= Related =

See also [[Branding History]]

Developer's Corner

2026-05-31T09:49:06Z

Hiran:

Branding

2026-05-31T09:48:27Z

Hiran: Removed redirect to Branding History

This page intends to describe where to find icons and other material, how to use them and in case of icon change lists all the places that need an update.
Information is based on the discussion in the [https://bb.oolite.space/viewtopic.php?t=21464&start=180 forum thread].

= Icon Change =

Currently this is just a list of locations we need to check. This may be enhanced by procedures to actually perform the changes.

== Oolite ==

oolite\debian\oolite-logo1.xpm
oolite\Doc\OoliteRS.odt
oolite\Documentation\docs\assets\oolite-logo.png
oolite\installers\win32\OoliteInstallerHeaderBitmap_ModernUI.bmp
oolite\installers\win32\Oolite.ico
oolite\installers\win32\Oolite-HDR.ico
oolite\installers\win32\OoliteInstallerFinishpageBitmap.bmp
oolite\Resources\Images\splash@2x.png
oolite\Resources\Images\WMicon.bmp
oolite\Resources\Images\splash.bmp
oolite\Resources\Images\splash.png

== Debug Console ==

oolite-debug-console\images\OoJSC.icns
oolite-debug-console\images\OoJSC.ico
oolite-debug-console\images\OoJSC16x16.png
oolite-debug-console\images\OoJSC24x24.png
oolite-debug-console\images\OoJSC32x32.png
oolite-debug-console\images\OoJSC48x48.png
oolite-debug-console\images\OoJSC64x64.png
oolite-debug-console\images\OoJSC96x96.png
oolite-debug-console\images\OoJSC128x128.png
oolite-debug-console\images\OoJSC192x192.png
oolite-debug-console\images\OoJSC256x256.png

== Oolite Starter ==

OoliteStarter/src/main/resources/icons/32px-Oolite-oxp-icon.png
OoliteStarter/src/main/resources/icons/OoliteIcon24.png
OoliteStarter/src/main/resources/images/Mr_Gimlet_Oolite.png
OoliteStarter/src/main/resources/oolite_logo.ico
OoliteStarter/src/main/resources/oolite_logo.png

== Others ==

- the logo on oolite.space (updates to the only-static and only-media branches in oolite-web)
- the favicon on oolite.space
- the logo on bb.oolite.space
- the favicon on bb.oolite.space
- the logo in the Microsoft Store
- the logo in the FlatHub
- Is there a central repository for AppImages? If so, there.
- the logo on the GitHub site.OoliteStarter/
- the logo on the wiki
- the favicon on the wiki

= Related =

See also [[Branding History]]

Talk:Branding History

2026-05-31T09:37:32Z

Hiran: Hiran moved page Talk:Branding to Talk:Branding History: Name to better match the page's purpose

Would it possible to attach all previous logos, icons, fonts ''etc''. to this page, or, at least, hyperlink on this page to repositories of all previous resource materials (with associated dates of having been in use, and record of first introduction/reveal) in this regard? Would it be possible to have this page be the dated, historical record of ''Oolite'' branding development and progression?

Example: [https://www.livejournal.com/allpics.bml?user=oolite ''Oolite (progress)'' LiveJournal Userpic] 2004apr07tue - ??? ([https://oolite.livejournal.com/profile proof of start-date])

My concern is that even on the initial 2006-01-03T18:26:46 post of the [https://wiki.alioth.net/index.php?title=Oolite&oldid=1294 ''Oolite''] wikipage, the original, blue logo (in use at the time of the initial posting of that page) has now been replaced by the new, red logo.

Let not our origins be forgotten, as happens to the location of Old Earth in GalCop Space! ...nor as happened during the [https://wiki.alioth.net/index.php/Great_Deletion Great Deletion].

Thanks for your consideration of this request.

--[[User:User2357|User2357]] ([[User talk:User2357|talk]]) 11:08, 4 January 2024 (UTC)

 

Thy eminence,

Phkb uploaded the new logo with the name of the old.

But. If you ''look'' at the ''pages'' with the files on them (if that is the correct description) you will see that the original is still there, somehow: [[:File:Oolite-logo3.png]] & [[:File:Oolite-logo2.png]].

Despite my supposed wizardly capabilities, I know not how to emblazon Seventh's original logo on another page here.

I beg, sir, to remain yours ''etc''.,

:''Cholmondeley 21:46, 4 January 2024 (UTC)''

 

Woo-hoo! Yee-Haw! Yippee-hi-ho-kah-yay! :D I thought those files had been lost. Thank you, Commander Cholmondeley. I'm no wiki-wizard either, but I'll have a go at it.

...

If I understand correctly, could the new, red-logo filenames perhaps be renamed differently, so that they do not clash with the original, blue-logo filenames, and, thus, hopefully, restore the blue logos on historical pages where they belong, and add the red ones to new pages? ...or am I not grasping the full complexity of the situation?

Commander Cholmondeley, on the Branding wikipage, you refer to File:Oosat 1.png, File:Oosat 2.png, and http://s248731467.onlinehome.us/ ... I agree that Oosat 2.png seems to be logoless, but it also seems to me to be unclear whether the Oosat site/pages were ever supposed to have any official ''Oolite'' logos in the first place that might require preservation. Oosat 1.png has an Elite Wiki logo in the bottom, left-hand corner, but I don't think that's what we're looking for...?

Also, on the Dizzy's ''Oolite'' Installers download page, that logo seems somewhat less "official", and might merely have been one that Dizzy designed for their own, personal purposes on their own, personal website; not necessarily to represent the ''Oolite'' comOonity as a whole. It does not seem as if it was ever a logo to be considered for display on any official ''Oolite'' website.

What I have in mind, is the preservation of the original logo(s) that Aegidian designed, and used on his websites/pages, and which might be more-closely compared to the ''Elite'' insignia designed by Philip Castle ([https://www.frontierastro.co.uk/Files/elite_misc.html]). The new, red logo seems to follow this tradition rather nicely, and, since the commOonity was consulted on the ''Oolite'' bulletin boards, and the red logo was incorporated on the official ''Oolite''.space website, I would think that few would argue against the red logo's right to preservation.

Attempting to preserve a file for every single ''Oolite'' logo out there, might not be practical and exhaustible/exhaustive; there will always be another one that we haven't included yet, and that is simply just more frustration than I am willing to sign up for. ...But ''official'' logos from original media... now those I'm willing to hunt down to the ends of the Earth. (...says I, not knowing what I'm getting myself into...)

*

I'll have to speak to my landlord regarding letting you be mine. He's not big on pets. Perhaps I can persuade him to let you stay in the basement. ''etc''. ;p (How am I ever to top such wonderfully-flowery language?)

--[[User:User2357|User2357]] ([[User talk:User2357|talk]]) 13:09, 7 January 2024 (UTC)

 

I would recommend that the two resolutions of the new, red logo be renamed Oolite-logo4-128.png and Oolite-logo4-256.png respectively.

How to get the Elite Wiki to display those, though, in stead of Oolite-logo3.png... I wouldn't know.

Hiran, in your original post of the Branding wikipage, you mentioned fonts... Which fonts did you have in mind? Where can those be obtained?

--[[User:User2357|User2357]] ([[User talk:User2357|talk]]) 04:28, 8 January 2024 (UTC)

----

Our past wiki-wizards were [[User:Winston|Winston]] (who set this up as the "Elite Wiki" back in the days before Oolite - hence our all-inclusive [[Main Page]] - and who still pays for it) and [[User:Maik|Maik]]. Both are programmers and both ''understand'' it. I merely have learned how to do a few things with it.

Phkb (also a programmer) uploaded the new logo into the "name-space" (if that is what it is) of the old. So every use of the old was replaced automatically by the use of the new without needing to manually tweak each and every one of them.

'''Use of dates on history-tab pages'''
I ''presume'' that (on the logo's "file:" page) clicking on the ''old'' date gives you the ''old'' logo file which you can then download and re-upload with a new name.

'''Notice the use of brackets in linking.'''

'''Single brackets''' for website pages. Uses a ''space'' ( ) to rename
'''Double brackets''' for wiki pages (avoids the little icon and avoids need for entire web address). Uses a ''pipe'' (|) to rename.

And you can do other things with pipes (in linking to User: pages). And with colons (in linking to Category: pages).

'''Dealing with "Category" pages can be complex.'''

The [[:Category:Lore]] page has sub-categories. And a linked [[Lore]] wiki page which appears at the top of the page list, not in the alphabetical ordering. ''If you examine the "Category" tags on each of those linked pages you should be able to work out how all this was done.''

Note that the addition of the colon to Category:Lore (-> :Category:Lore) immediately above. That prevents this talk page also being tagged with the Lore category and merely links to that page instead.

You might find it helpful to browse the [[Special:Categories|list of categories]] and try and make sense of them.

[[User:Debresser|Debresser]] seems to have spent quite some time pruning the categories to make more sense. I've not done so as I don't yet feel that I have the knowledge to do a decent job.

The point of these pages seems to be "easy" indexing - where you include a page in an index by merely tagging it, rather than having to manually update an index each time the page changes (as would need to be done with my various manually collated lists of relevant OXPs dotted around this wiki).

:''Cholmondeley 10:15, 8 January 2024 (UTC)''
----

 

Proposal: I am willing to delete the new, red logo image-files from the ''Elite'' Wiki, rename the highest-resolution version to "''Oolite''-logo4.png", re-upload it, and then edit and replace every single last little hyperlink to ''Oolite''-logo2.png and ''Oolite''-logo3.png in the '''entire''' ''Elite'' Wiki -- on all of five ''other'' hyperlinking wikipages. ;) (Only the highest-resolution version is required, since the ''Elite'' Wiki apparently has the capability to scale images.)

[https://wiki.alioth.net/index.php/Special:WhatLinksHere/File:Oolite-logo2.png Pages that link to ''Oolite''-logo2.png]

[https://wiki.alioth.net/index.php/Special:WhatLinksHere/File:Oolite-logo3.png Pages that link to ''Oolite''-logo3.png]

Howzat? Would this be acceptable to all? :)

(Then we would be able show all the historical logo-images on this Branding page as well, in stead of merely hyperlinking to the source-file pages. :D )

--[[User:User2357|User2357]] ([[User talk:User2357|talk]]) 07:27, 10 January 2024 (UTC)

 

The file-delete option that I thought I saw previously, apparently is not available to me (anymore?)... There goes my perfect plan in the pants! :/

This was now discovered after uploading a new version of one of the logo-image files I had uploaded recently, and the new version of the image NOT being replaced into the location where the file is called... This is frustrating. ...when functionality apparently does not function as it is supposedly supposed to. Hm. :/

--[[User:User2357|User2357]] ([[User talk:User2357|talk]]) 06:29, 15 January 2024 (UTC)

You need to speak with Maik (if he has any spare time) about deletion - he understands how it works, and understands rather more about how this wiki works than I do. I'm unhappy to delete something when I don't understand what the consequences are - and I don't. Look what happened when Hiran started deleting stuff on GitHub a couple of months ago - and he's a professional programmer! (https://bb.oolite.space/viewtopic.php?f=2&t=21457)

::''Cholmondeley 08:55, 15 January 2024 (UTC)''

 

Nah. I don't think I'll bother Maik.

The interface is less than what is optimal for all our spare times, at the moment.

Been looking at fandom.com a bit... Not sure if their copyleft policy clashes with any ''Oolite'' licensing, though.

On the other hand, (1) the ''Elite'' Wiki is here at alioth.net already (thanks to Dylan Smith); (2) migrating it... huge job, methinks; (3) not sure exactly why the grass seems greener on the other side, but it might be, as is usual, because of more plentiful manure... :/

I guess what I'm saying, is: should the alioth.net ''Elite'' Wiki ''ever'' become borked beyond all practicality anymore, fandom.com might be an alternative that could be considered. In the meanwhile, let's keep what we know we've got.

--[[User:User2357|User2357]] ([[User talk:User2357|talk]]) 13:36, 19 January 2024 (UTC)

Talk:Branding

2026-05-31T09:37:32Z

Hiran: Hiran moved page Talk:Branding to Talk:Branding History: Name to better match the page's purpose

#REDIRECT [[Talk:Branding History]]

Branding History

2026-05-31T09:37:31Z

Hiran: Hiran moved page Branding to Branding History: Name to better match the page's purpose

[[File:Oolite-logo3.png|right]]
= Introduction =
This page attempts to record and preserve the historical heritage of ''Elite''/''Oolite'' branding, specifically in terms of logos, icons and fonts. [https://frontierastro.co.uk/ FrontierAstro] is very useful in this regard.

Fonts came up from the OpenOffice documentation (Reference Sheet, etc.) that is distributed in PDF format. As soon as the PDFs were generated using open-source software only, it became apparent that the documents were based on fonts only available in Microsoft Windows operating systems. From that moment on, alternatives had to be found.

This page focuses on ''Elite'' (and its descendant ''Oolite'') since (1) it is the origin of all the related brands, (2) and it has had a multitude of different versions, many of them introducing variations on the theme, while (3) the ''Frontier'' games do not seem to have had any significant brand-variations along the way. For completeness, though, the ''Frontier'' logos and icons will also be included, but [https://duckduckgo.com/?q=elite+dangerous+logos&va=p&atb=v355-1&iax=images&ia=images ''Elite: Dangerous''] has an impractically-large amount of branding for the purposes of the simple historical-record intended here.

= ''Elite'' branding history =
1984... [[Classic_Elite|Elite]]... [[David Braben]], [[Ian Bell]], [[Robert Holdstock]], and... Philip Castle.

The first three names were responsible for the programming and the documentation ([http://www.elitehomepage.org/playguide.htm ''Elite'' Players' Guide]; [https://archive.org/details/elite_acornsoft_manual/mode/1up?view=theater ''The Space Trader's Flight Training Manual''] and [https://openretro.org/file/ec43acc68931c84951a13b6285ed4ccd64b5b787 ''The Dark Wheel''], Stock Code Numbers for the latter: SBG38/B1 and SBG38/B3, respectively, etc.). However, the ''Elite'' simulator would probably not have had such a successful market-entrance had it not been for the fourth gentleman's eye-catching skills as an airbrush artist.

On the [https://www.frontierastro.co.uk/Files/elite_misc.html "FrontierAstro ''Elite'' - Various Items"] page, approximately halfway down -- as if "quasi-[https://www.languagehumanities.org/what-is-a-chiastic-structure.htm chiastically]" in the central focal-point of the nine topic-sections -- he is briefly introduced... but his work is pretty much everywhere on that page.

On [http://www.iancgbell.clara.net/elite/ Ian Bell's website], in the ''Elite'' Archives, in the file [http://www.elitehomepage.org/archive/a4120001.png a4120001.png], the "DECEMBER 1984" Acorn News report (scan), in the second column, third paragraph; and in [https://www.reddit.com/r/IAmA/comments/15od2s/comment/c7qdaj8/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button David Braben's 2013 reddit ''Elite: Dangerous'' AMA], [https://en.wikipedia.org/wiki/Philip_Castle Philip Castle] is authoritatively identified as the designer of the original ''Elite'' logo. (The [https://mythology.net/mythical-creatures/griffin/ "Griffin thing"], as mentioned by Braben, as a supposed element of the ''Elite'' logo, is debatable, though.)

= ''Oolite'' branding history =
> 7 April 2004, [[User:Aegidian|Aegidian]]'s [[Aegidian_devlog|''Oolite'' (progress)]] [https://oolite.livejournal.com/profile LiveJournal] introduced the [https://wiki.alioth.net/index.php/File:Oolite-logo1.png ''Oolite'' userpic], which can be downloaded from that [https://www.livejournal.com/allpics.bml?user=oolite page] (right-click > Save Image As...) as a 100 pixels x 100 pixels .png image.

> 16:15, 3 January 2006, Rxke apparently uploaded to the ''Elite'' Wiki a 128 x 128 [https://wiki.alioth.net/index.php/File:Oolite-logo2.png ''Oolite'' logo] version of the userpic.

> 12:57, 7 May 2011, Ahruman uploaded to the ''Elite'' Wiki the 256 x 256 [https://wiki.alioth.net/index.php/File:Oolite-logo3.png "New (2011) ''Oolite'' icon"] by Eugene Chernyakov (seventh).

> Mon Oct 23, 2023 12:39 am, on the ''Oolite'' Bulletin Boards, in the Discussion forum, the [https://bb.oolite.space/viewtopic.php?f=2&t=21464 "New splash screen and icon"] thread was posted by phkb, in which was suggested that the ''Oolite'' splash screen and icon had been around for a while now, and it was proposed that they were about due for a refresh. This discussion led to the new, red versions of the [https://wiki.alioth.net/index.php/File:Oolite-logo2.png 128 x 128] and [https://wiki.alioth.net/index.php/File:Oolite-logo3.png 256 x 256] logo-images, and the new black-and-white version of the [https://wiki.alioth.net/index.php/File:Oolite-IconBW.png ''Oolite'' icon], all three uploaded to the ''Elite'' Wiki as new version of the old filenames six days later by Phkb. The new, red logo was also incorporated in the official [https://oolite.space/ oolite.space] website.

= Caveat & HowTo =

The ''Elite'' Wiki allows the uploading of new versions of old files. However, "new version" should be defined and understood as "improved version", rather than "different version", where "improved" could mean "increased resolution", or "more universally-applicable file format", or other more subtle edits, in order to establish the [https://wiki.alioth.net/index.php/File:Elite-logo1988-3_manual_front_cover_(rotated).jpg originally-intended, '''best'''] version of the file. Uploading a ''different'' version of an existing file causes that file to be replaced universally throughout the entire ''Elite'' Wiki -- even on old, "history" pages of ''Elite'' wikipages (e.g.: on the very first, 05:22, 14 February 2006 version of the [https://wiki.alioth.net/index.php?title=Oolite_Main_Page&oldid=3181 ''Oolite'' Main Page] the original, blue, 2006 logo had been replaced by the new, red, 2023 logo). This is not a black-and-white, easily-defined, well-behaved, simple and straight-forward issue, and there could, arguably, be many ambiguous scenarios and exceptions to whatever guidelines might have been imagined.

Therefore -- ''if in doubt'' -- it is safer, in terms of the preservation of the historical integrity of the ''Elite'' Wiki (although it also requires more work), to upload a "new" version of an existing file under a correspondingly-new filename with the intention of replacing the old version on subsequent (and not previous, historical) wikipages. When a "new" version of an existing file is considered for upload, the following methodology is recommended.

'''HowTo'''

On an ordinary ''Elite'' wikipage, in the left-hand margin, under "tools" > "Special pages" > "Media reports and uploads" > "File list", in the "Search for media name" search box, enter a known portion of the filename (e.g.: "logo" or "icon"), click the "Include old versions of files" tick-box and then the "Go" button; then click the name-hyperlink that is associated with the desired thumbnail. Then, again, in the left-hand margin, under "tools" > "What links here", in order to determine where on which wikipages which hyperlinks or references would potentially need to be updated to a new filename, so that history pages will not unintentionally be [https://en.wikipedia.org/wiki/Ministries_in_Nineteen_Eighty-Four#Ministry_of_Truth Minitrue]-redacted.

Therefore, in an attempt (1) to prevent a loss of the commOonity's heritage on ''Elite'' Wiki history pages, and (2) to facilitate easier searching for older logo-versions, it is recommended that future, new-logo designs be named according to, and uploaded under filenames conforming to the established naming-scheme of "''Oolite''-logo#", where # is the next number in the sequence, and that all of the hyperlinks throughout the ''Elite'' wiki be updated accordingly. It is recommended that only a single, highest-resolution logo-image be uploaded, since the ''Elite'' Wiki has the functionality to scale the logo images: <nowiki>[[File:oolite-logo#.png|196px]]</nowiki>. A similar, numbered naming-scheme, although not implemented as yet, is also recommended for icons.

If an older logo (or icon) might be required for any purpose, the [https://wiki.alioth.net/index.php/Special:ListFiles?limit=1000&ilsearch=logo&user=&ilshowall=1 "logo" File list search-page] is recommended (substitute "icon" in stead of "logo", if required). Include old versions of files.

= Original Logos and Icons =

''' ''Elite'' '''

''Elite'' logos have been sourced from box art, manual covers, half-title, title and other pages, and ''The Dark Wheel'''s front covers. It appears that other, minor media, included in any package, only have variations on the various themes in that package. The logos below are identified by, and arranged according to their dates and usage of first appearance. Hover over the images for descriptions. Consult [https://frontierastro.co.uk/ FrontierAstro] to see how some of these logos have been re-used for different elements of various versions.

1984
[[File:Elite-logo1984-1 box art & The Dark Wheel front cover.jpg|128px|box art & The Dark Wheel front cover]]
[[File:Elite-logo1984-2 manual front cover.png|128px|manual front-cover]]
[[File:Elite-logo1984-3 manual half-title page.png|128px|manual half-title page]]

1985
[[File:Elite-logo1985-1 box art & manual front cover.png|128px|box art & manual front-cover]]
[[File:Elite-logo1985-2 Spectrum manual title page.png|128px|Spectrum manual title-page]]
[[File:Elite-logo1985-4 The Dark Wheel front cover (rotated).jpg|128px|The Dark Wheel front cover]]

1988
[[File:Elite-logo1988-1 box art.png|128px|box art]]
[[File:Elite-logo1988-3 manual front cover (rotated).jpg|128px|manual front-cover]]

1991
[[File:Elite-logo1991-1 ArcElite manual front cover.png|128px|ArcElite manual front-cover]]
[[File:Elite-logo1991-2 ArcElite manual title page.png|128px|ArcElite manual title-page]]
[[File:Elite-logo1991-3 Elite Plus UK box art & manual front cover.png|128px|Elite Plus UK box art & manual front-cover]]
[[File:GalCop-logo1991-4 Elite Plus manual.png|128px|Elite Plus manual]]
[[File:Tri-Alliance-logo1991-5 ArcElite manual.png|128px|ArcElite manual - Tri-Alliance logo]]

Some logos were originally designed skew by a few degrees anticlockwise. The original, skew versions are available from the [https://wiki.alioth.net/index.php/Special:ListFiles?limit=1000&ilsearch=logo&user=&ilshowall=1 "logo" File list search-page]. For ease of comparison, and for streamlining this page's layout, only the upright-rotated logos are shown here.

The 1991 ArcElite manual title-page and 1984 manual front-cover logos seem to be the cleanest, for the purposes of using them as potential templates for future designs.

From time to time, among the logos, there does seem to be a subtle motif of "ascending to the next level" (3D), "accelerating", and then also "breaking out of the frame" and "transcending of boundaries", as it were; c.f.: 1984 box art & ''The Dark Wheel'' front cover (even extending off-page), 1985 ''The Dark Wheel'' front cover, and 1988 manual front-cover. The graphics for the [https://ia601304.us.archive.org/19/items/Elite_Plus_Manual/Elite_Plus_Manual_text.pdf 1991 ''Elite Plus'' manual's] title page, Cobra Mk III (p. 13), ''Observer's Guide to Ships in Service'' (pp. 67 - 86), and the ''Imprint'' novella's title page (p. "87"), all subtly communicate this repeated motif as well. In comparison with the other logos, and within itself, the 1991 ''Elite Plus'' simulator's logo also adds an extra, juxtaposed element of realism...

''' ''Oolite'' '''

2004
[[File:Oolite-logo1.png|128px|Aegidian LiveJournal 100px x 100px userpic]]

''' ''Frontier'' ''' (for completeness)

1993
[[File:Frontier- Elite II-logo1993 box art.png|128px|box art]]
[[File:Frontier- Elite II-logo1993 manual front cover.png|128px|manual front-cover]]

1995
[[File:Frontier- First Encounters-logo1995 box art.jpg|128px|box art]]
[[File:Frontier- First Encounters-logo1995 manual front cover.jpg|128px|manual front-cover]]

= Logos and Icons on the ''Elite'' Wiki =

''' ''Elite'' '''

2006

Wiki functionality is broken for me. I did what I could, to the best of my abilities, but I am apparently not capable/allowed to do what needs to be done here further anymore. Thanks. It's been fun, while it lasted. I'll leave this in the capable hands of other, more powerful people now.

''' ''Oolite'' '''

2006

2011

2023

''' ''Frontier'' ''' (for completeness)

2006

= Fonts =

The font used in-game is a custom, mono-spaced font. ''Oolite'' does not work with Truetype or Freetype fonts.

The fonts in the documentation are ...

The fonts used in the website oolite.space are ...

The fonts used in the wiki are ...

The fonts used in the forum are ...

[[Category:Classic]][[Category:Oolite]][[Category:Factual]]

Branding

2026-05-31T09:37:31Z

Hiran: Hiran moved page Branding to Branding History: Name to better match the page's purpose

#REDIRECT [[Branding History]]

Oolite Instruction Manual

2026-05-14T21:33:59Z

Hiran: /* Playing the game */

==Installing the game==
* [[Running Oolite-Mac|Build, Install and run Oolite on Mac OS X]] (Oolite v.1.92 is not available for the AppleMac)
* [[Running Oolite-Linux|Build, Install and run Oolite on Linux]]
* [[Running Oolite-Windows|Build, Install and run Oolite on Windows]]
* [[Running Oolite-Fedora Core 5|Build, Install and run Oolite on Fedora Core 5]]
* [[Running Oolite-Unix|Build, Install and run Oolite on BSD and Irix]]

Note that from release 1.77 onwards two different release configurations are available for download: "deployment" which includes full optimisation and is most suitable for those just wanting to play the game, and "test" which includes additional debugging and development tools, and is intended for OXP development. If you are unsure, we recommend the "deployment release" - it is easy to convert it into a "test release" later.

=== More general links ===
* [https://bb.oolite.space/viewtopic.php?f=2&t=16255 Source Code and Ideas question] (2014: v.1.77.1) - handling GitHub, how to change maximum amount sellable, elite rankings, legal status

==A background to the game==
* [[Alien Items]] - A series of short stories which set the scene.
* [http://www.alioth.net/Fiction/oolitestory.pdf The Virtuous Misfortune] - A story that sets the scene (now included in "Alien Items")
* [[Status Quo]] - Elite came with a Novella called 'The Dark Wheel', which set the scene for that game. 'Status Quo' aims to do the same thing for 'Oolite', introducing Commander Jamesons to the 'Ooniverse'... Status Quo is the first part of a five part series known as the [[Oolite Saga]].
* [[Calliope|Calliope - a Captain Hesperus adventure]] - An episode from the unorthodox life of the commander of the ''Dubious Profit''
* [[Powers and Organisations]] - Some histories of the various corporations and powers, both legal and illicit, that exist in the Oolite Galaxies.
* [[Mr Gimlet]] - A wise Blue Frog aboard Lave Station has some tips for new Commanders.
* The ''[[Rough Guide to the Ooniverse]]'' – A brief overview of the inhabitants, customs and cultures of Lave and other nearby worlds.

==Playing the game==
* [https://github.com/OoliteProject/oolite/blob/master/Doc/OoliteRS.odt Download OoliteRS.odt] or access [https://oolite.readthedocs.io/en/latest/reference/ online] - Essential info reference sheet for a quick start
* Ship's Manual - available through the [[Ship's Library OXP]]
* [[Pilot's Reference Manual]]
* [[Oolite Docking Clearance Protocol (v1.72 or later)|Docking Clearance Protocol]]
* [[How to Dock|How to Dock]]
* [[Oolite Equipment|Equipment]] (& [[Priming Equipment]] for OXPs)
* [[Oolite Trading|Trading]]
* [[Career Options]]
* [[Oolite Tactics|General Combat Tactics]]
:* [[Dealing with piracy (Oolite)|How to deal with pirates]]
:* [[Dealing with Thargoids|How to deal with Thargoid ambushes]]
:* [[Laser tactics]]
:* [[Missile tactics]]
:* [[Using weapons of mass destruction|WMD tactics]]
* [[IFF system]]
* [[Fuel Scoops|Scooping fuel and cargo]]
* [[Contracts]]
* [[Oolite Keyboard Controls|Keyboard Controls]]
* [[Dizzy's guide to Setting up Joystick Axis Profiles|Setting up Joystick Axis Profiles]]
* [[Oolite Voice Control|Voice Control]]
* [[Oolite Missions|Missions]]

==Technical help and troubleshooting==
* [[Location of Oolite saved settings]]
* [[Hidden Settings in Oolite]]
* [https://bb.oolite.space/ Oolite Bulletins Forum]
* [[Oolite FAQ|Oolite Frequently Asked Questions (FAQ)]]
* [[Joystick problems (Linux)]]

[[Category:Oolite]][[Category:Help pages]]