Developer's Corner - Revision history

Cholmondely: Retagged as major page in "Oolite Development"

2026-07-14T15:31:52Z

Retagged as major page in "Oolite Development"

Hiran at 07:02, 9 July 2026

2026-07-09T07:02:53Z

Hiran at 06:10, 9 July 2026

2026-07-09T06:10:00Z

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

2026-07-03T16:59:21Z

‎The build system (architecture)

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

2026-06-30T17:02:51Z

‎The build system (architecture)

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

2026-06-30T16:54:13Z

‎The build system (architecture)

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

2026-06-28T17:40:30Z

‎The build system (architecture)

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

2026-06-27T16:45:28Z

‎The build system (architecture)

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

2026-06-27T16:40:22Z

‎The build system (architecture)

Hiran at 13:08, 26 June 2026

2026-06-26T13:08:28Z

@@ Line 30: / Line 30: @@
 |}
-==Releasing the code==
+== 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]].
 == Hints ==
@@ Line 45: / Line 43: @@
 To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules

@@ Line 9: / Line 9: @@
 * [[Cross Platform IDEs]]
 * [[Compiling with Clang instead of gcc]] (Windows/Linux)
-* [[The build system]]
+* [[Oolite build system]]

@@ Line 9: / Line 9: @@
 * [[Cross Platform IDEs]]
 * [[Compiling with Clang instead of gcc]] (Windows/Linux)
 == OS Specific parts ==

← Older revision		Revision as of 16:59, 3 July 2026
Line 13:		Line 13:

	Here is the result of this forum thread: [https://bb.oolite.space/viewtopic.php?t=22148 gitversion.sh / meson.build changes]		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		# pre-build

@@ Line 27: / Line 27: @@
          "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/"
+         "information_url": "https://oolite.space/",
+     }

@@ Line 32: / Line 32: @@
 </p>
 # build
-# testing unpackaged
+#* setup/configure
 # post-build
 # packaging

@@ Line 18: / Line 18: @@
 #* download sourcecode<p>This should include oolite sourcecode as well as the code needed for external dependencies.</p>
 #* install required dependencies<p>The baseline discussed at [https://bb.oolite.space/viewtopic.php?p=304440 viewtopic.php?p=304440] should make this part a lot easier./p><p>It includes building external deps that are not available in the build environment. Targets that use 'modern builds' for example require gnustep objc2.</p><p>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.</p>
-#* changes to sourcecode to allow succesfull builds<p>example : 1.92-maintenance has 2 files that screw up things at runtime for some targets. Deleting those files is the only option.</p>
+#* changes to sourcecode to allow succesfull builds<p>example : 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.</p>
-#* set/update values that can not be determined before build time.<p>This includes things like sourcecode url, build environment, git commit hash</p>
+#* set/update values that can not be determined before build time.<p>This includes things like sourcecode url, build environment, git commit hash.</p><p>These values shall be passed in a JSON file inside the build directory. An example build file can look like this:
 # build
 # testing unpackaged

@@ Line 15: / Line 15: @@
 # pre-build
 # build
 # testing unpackaged