Developing Oolite - Revision history

Another commander: /* Current way to do it */

2025-12-18T20:45:26Z

‎Current way to do it

Cholmondely: /* Links */ Added another

2025-01-29T19:55:11Z

‎Links: Added another

Hiran: /* Setting up your development environment */

2024-09-22T09:34:27Z

‎Setting up your development environment

Another commander: /* Current way to do it */

2024-09-13T10:07:20Z

‎Current way to do it

Cholmondely: /* Links */ Added a_c_'s thread about Steam

2024-05-20T05:55:09Z

‎Links: Added a_c_'s thread about Steam

Phkb: Updating BB links

2024-02-29T01:34:35Z

Updating BB links

Cholmondely: Added note on AppleMac

2023-12-20T09:36:17Z

Added note on AppleMac

Hiran: /* Setting up your development environment */

2023-10-19T14:22:33Z

‎Setting up your development environment

Hiran: /* Documentation */

2023-10-19T14:20:45Z

‎Documentation

Hiran: /* Documentation */

2023-10-19T14:19:13Z

‎Documentation

@@ Line 113: / Line 113: @@
 Alternatively, you can use the same Development Environment we deploy on github to produce the Windows nightly pre-release builds. This is guaranteed to always be the most recent and updated version, but it is a significantly bigger download. You can get it from https://github.com/OoliteProject/oolite-windows-build-env/releases/download/latest/DevelopmentEnvironment.zip
@@ Line 118: / Line 120: @@
-Download the environment and unzip it to a folder of your choice. IMPORTANT: The zip file you downloaded must be decompressed maintaining the folders' path structure, check your unzip program's documentation if you are not sure how to do this. Also note that in the unlikely case that your system is using drive letter O:, you will need to edit the files msys_x2/1.0/msys.bat and msys_x2/1.0/etc/fstab and change the references to o: to an unused drive letter. MORE IMPORTANT: Do not install this in a path containing spaces. We have had cases where the environment failed to work when installed in locations such as My Documents, Program Files etc.
+If building with the legacy GCC 4.7.1, download the environment and unzip it to a folder of your choice. IMPORTANT: The zip file you downloaded must be decompressed maintaining the folders' path structure, check your unzip program's documentation if you are not sure how to do this. Also note that in the unlikely case that your system is using drive letter O:, you will need to edit the files msys_x2/1.0/msys.bat and msys_x2/1.0/etc/fstab and change the references to o: to an unused drive letter. MORE IMPORTANT: Do not install this in a path containing spaces. We have had cases where the environment failed to work when installed in locations such as My Documents, Program Files etc.
@@ Line 130: / Line 132: @@
 ) Mingw32 -> Mingw.
 Reverse-rename to return to the 64-bit configuration. Never, ever mix 32-bit Devlibs with 64-bit Mingw or vice-versa. Expect build failure if you do so.

← Older revision		Revision as of 19:55, 29 January 2025
Line 296:		Line 296:

	* [https://bb.oolite.space/viewtopic.php?t=21215 Steam-ready (almost)] (2022-24)		* [https://bb.oolite.space/viewtopic.php?t=21215 Steam-ready (almost)] (2022-24)
		+
		+	*[https://bb.oolite.space/viewtopic.php?t=21539 How to access Oolite build artifacts on Github] (2023)

	[[Category:Oolite]] [[Category:Oolite Development\| ]]		[[Category:Oolite]] [[Category:Oolite Development\| ]]

← Older revision		Revision as of 09:34, 22 September 2024
Line 95:		Line 95:

	= Setting up your development environment =		= Setting up your development environment =
−
−	~~== On Linux ==~~
−
−	~~Do as you wish :-)~~
−
−	~~I use vim + youcompleteme.~~
−
−	~~There's no IDE on linux managing objective-c (at least not Eclipse and Intellij).~~
−	~~Auto-completion doesn't work in most of them because the xCode libraries aren't available (they're on OS X).~~
−
−	~~The only plugin for objective-c on eclipse is discontinued.~~
−
−	~~You can see the call hierarchy in the doxygen documentation at https://ooliteproject.github.io/oolite/~~
−
−	~~Some use Emacs.~~

	= Building =		= Building =

← Older revision		Revision as of 10:07, 13 September 2024
Line 126:		Line 126:
	https://drive.google.com/file/d/1u1IvBxiQjNvtrFs_2POaRP3IZhAi46N0/view?usp=sharing		https://drive.google.com/file/d/1u1IvBxiQjNvtrFs_2POaRP3IZhAi46N0/view?usp=sharing
	The package contains the Objective-C compiler plus Posix environment (MinGW/MSYS), the Git package version 2.16.2 required for checking out and updating the source code and the required gnustep-base 1.20.1 files. No other downloads will be required.		The package contains the Objective-C compiler plus Posix environment (MinGW/MSYS), the Git package version 2.16.2 required for checking out and updating the source code and the required gnustep-base 1.20.1 files. No other downloads will be required.
		+
		+	Alternatively, you can use the same Development Environment we deploy on github to produce the Windows nightly pre-release builds. This is guaranteed to always be the most recent and updated version, but it is a significantly bigger download. You can get it from https://github.com/OoliteProject/oolite-windows-build-env/releases/download/latest/DevelopmentEnvironment.zip

@@ Line 307: / Line 307: @@
 == Links ==
 * [https://bb.oolite.space/viewtopic.php?p=270121#p270121 Building Spidermonkey (2020)]
 [[Category:Oolite]] [[Category:Oolite Development| ]]

@@ Line 5: / Line 5: @@
 == Before you begin ==
-If you do not know Objective C, see [http://aegidian.org/bb/viewtopic.php?f=7&t=10525 I want to help develop Oolite] (2011).
+If you do not know Objective C, see [https://bb.oolite.space/viewtopic.php?f=7&t=10525 I want to help develop Oolite] (2011).
 == Cloning or forking? ==
@@ Line 255: / Line 255: @@
 If you want to edit the source, Notepad++ has good Objective-C support and is free: [http://notepad-plus.sourceforge.net/]
-Also see the Oolite-PC forum: [http://www.aegidian.org/bb/viewforum.php?f=8]
+Also see the Oolite-PC forum: [https://bb.oolite.space/viewforum.php?f=8]
 == Building Oolite-Linux ==
@@ Line 280: / Line 280: @@
 * The makefile is called GNUmakefile rather than 'Makefile'; this seems to be the convention for GNUstep applications. If you are not using GNUmake, then you will probably need to 'make -f GNUmakefile'. However, it is recommended that you install gmake if you are using a platform (BSD) that doesn't include GNU make (it's a dependency for GNUstep anyway). The build process first builds all the Objective-C source (source code files end in '.m' which is the standard file extension for Objective-C) into the executable oolite.app/oolite and then copies the data into oolite.app/Contents.
-* A new dependency on the SpiderMonkey JavaScript v1.70 library was introduced on SVN revision 1157. This requires some attention regarding the Linux build process. The full instructions on building the game successfully with JavaScript 1.70 on Debian can be found in the following forum post:<br />http://aegidian.org/bb/viewtopic.php?p=42188&highlight=#42188
+* A new dependency on the SpiderMonkey JavaScript v1.70 library was introduced on SVN revision 1157. This requires some attention regarding the Linux build process. The full instructions on building the game successfully with JavaScript 1.70 on Debian can be found in the following forum post:<br />https://bb.oolite.space/viewtopic.php?p=42188&highlight=#42188
 * As of 1.73, a new 'Makefile' has been added to the project to simplify building Oolite.  Assuming your system has all required build dependencies installed (as outlined above), you can build debug and optimised copies of Oolite with the following commands.  The included Spidermonkey dependency is automatically built as well.  For a full list of targets, use 'make -f Makefile help'.
@@ Line 290: / Line 290: @@
 Several bugs have been found with gnustep-base1.19.3 which affect Oolite to a greater or lesser extent.  As older versions of several popular Linux Distributions ship with this version of GNUstep, it is highly recommended that you compile and install a known good version of GNUstep for development. gnustep-base1.18 is known to be good.  The current trunk (gnustep-base1.21.1) appears to also be ok.
-This [http://aegidian.org/bb/viewtopic.php?t=8008&highlight= forum post] details how to build and install gnustep for developing Oolite.
+This [https://bb.oolite.space/viewtopic.php?t=8008&highlight= forum post] details how to build and install gnustep for developing Oolite.
 <div style="clear:both"></div>
@@ Line 303: / Line 303: @@
 That said, Oolite is not necessarily the best project to start with; taking a look at [http://developer.apple.com/documentation/Cocoa/Conceptual/ObjCTutorial/index.html Apple’s] or [http://www.gnustep.it/pierre-yves/index.html GNUstep’s] tutorials. (The latter appears to be a rip-off– er, adaptation of the former.) These are geared towards GUI apps, though.
-[[User:Ahruman|Ahruman]], 2007 from [http://www.aegidian.org/bb/viewtopic.php?p=32138#p32138 Learning Objective-C]
+[[User:Ahruman|Ahruman]], 2007 from [https://bb.oolite.space/viewtopic.php?p=32138#p32138 Learning Objective-C]
 == Links ==
-* [http://www.aegidian.org/bb/viewtopic.php?p=270121#p270121 Building Spidermonkey (2020)]
+* [https://bb.oolite.space/viewtopic.php?p=270121#p270121 Building Spidermonkey (2020)]
 [[Category:Oolite]] [[Category:Oolite Development| ]]

@@ Line 112: / Line 112: @@
 = Building =
 == On Windows ==
 === Current way to do it ===

@@ Line 107: / Line 107: @@
 The only plugin for objective-c on eclipse is discontinued.
-You can see the call hierarchy in the doxygen documentation.
+You can see the call hierarchy in the doxygen documentation at https://ooliteproject.github.io/oolite/
 Some use Emacs.

@@ Line 92: / Line 92: @@
 Note that this will generate the Mac source documentation by default. For Linux and Windows, you will also have to pass the appropriate defines (e.g. OOLITE_WINDOWS, OOLITE_SDL etc.) to Doxygen.
-If you don't want to install Doxygen, you can download an example early 2018 snapshot of the Windows source code documentation from [http://wiki.alioth.net/img_auth.php/8/8c/Doxygen_OoliteSource.oxz ''here'']. Once downloaded, just change the extension to .zip, unzip to any folder normally and run the '''index.html''' file inside the folder named html.
+If you don't want to install Doxygen and generate it yourself you can download the documentation from Github, or browse it directly on https://ooliteproject.github.io/oolite/.
 = Setting up your development environment =

@@ Line 65: / Line 65: @@
 The documentation is automatically generated from the source code.
 When generated, it's 700mb heavy !
 == Pre-requisites ==