Oolite

Oolite is an open source Elite clone on steroids. While it can run just like the original but on modern computers it can also be vastly modified through Oolite Expansion Packs. Homepage: Wiki: Forum: Documentation: Oolite can be heavily customized via expansions. These modify the gameplay, add ships, improve graphics - the possibilities are almost endless: Please join the Oolite Bulletin Board, a friendly community of Oolite fans and developers! The Windows NSIS installer is named OoliteInstall-XXX-win.exe where XXX is a version number. Double click the downloaded file to run the installer. Linux has Flatpak and AppImage versions. The Flatpak is named space.oolite.Oolite XXX.flatpak where XXX is a version number. Many Linux package managers support Flatpak so you should be able to double click the downloaded file to install it. The AppImage is named Oolite XXX-x86 64.AppImage where XXX is a version number. Download this file to where you would like it stored, ./mk.sh it executable and run, for example by typing We welcome developers to work on Oolite! If you wish to build the project from source, please follow the instructions below. Note that the scripts require sudo for activities like installing dependent libraries built from source and for installing packages on some Linux distros. If you run into difficulties, you can seek help on the Oolite Bulletin Board. The Oolite source is available from GitHub. The first step is to install git if you don't already have it installed as it is required to obtain and build Oolite. With Git installed, check out the Oolite repository: This will install MSYS2 which provides various MinGW environments. You will need to enter the install location for MSYS2 and whether you want the Clang build (recommended) or GCC build. The Clang build uses the UCRT64 environment, while the GCC build uses the MINGW64 environment. By default, the above two commands will install to $HOME/.local, but you can supply an argument system or build to specify /usr/local or the project build folder respectively. When installing to /usr/local, sudo is used by default, but you can supply a further argument to specify an alternative like doas. The underlying build system is Meson, but it is recommended to build via the mk.sh script which also allow you to pass meson setup, compile, configure and install flags. Type the following for help: Oolite has various build types: "dev" : Keeps debug symbols in the binary. "deployment" : Intended for production builds. Removes debug symbols from the binary, but makes them available in a separate symbols file. "test" : Used for test releases; supports the debug console, which expansion developers use to debug their OXPs. Removes debug symbols from the binary, but makes them available in a separate symbols file. Optionally you can pass --setup-flags and/or --compile-flags to pass specific options to meson. The completed build (executable and games files) can be found in the build/meson dev/oolite.app directory. build dev runs 2 actions which can be run independently: setup dev which runs meson setup and compile dev which runs meson compile. Intel-based Macs can run old builds of Oolite, but current Macs are unsupported. It is hoped that they can be supported in future.