Compiling with Clang instead of gcc - Revision history

Cholmondely: Added another link

2025-11-04T10:43:14Z

Added another link

Mcarans: /* Links */

2025-10-29T07:15:31Z

‎Links

Mcarans at 07:14, 29 October 2025

2025-10-29T07:14:47Z

Cholmondely: Added Links

2025-10-28T13:15:57Z

Added Links

Cholmondely: Tagged as Oolite Development

2025-10-28T13:10:00Z

Tagged as Oolite Development

Mcarans at 01:42, 28 October 2025

2025-10-28T01:42:55Z

Mcarans at 01:02, 28 October 2025

2025-10-28T01:02:45Z

Mcarans at 23:10, 27 October 2025

2025-10-27T23:10:58Z

Mcarans: Clarification

2025-10-27T23:08:32Z

Clarification

Mcarans: -fobjc-runtime=gnustep-1.9 is now in Gnumakefile

2025-08-03T21:34:41Z

-fobjc-runtime=gnustep-1.9 is now in Gnumakefile

@@ Line 67: / Line 67: @@
 == Links ==
 *[https://bb.oolite.space/viewtopic.php?t=21898 BB thread: Clang build ABI 1.9 Linux only (+latest gnustep-base) (solved)] (2025)
 [[Category:Oolite Development]]

@@ Line 67: / Line 67: @@
 == Links ==
-*[https://bb.oolite.space/viewtopic.php?t=21898 BB thread: Clang build ABI 1.9 (+latest gnustep-base) (solved)] (2025)
+*[https://bb.oolite.space/viewtopic.php?t=21898 BB thread: Clang build ABI 1.9 Linux only (+latest gnustep-base) (solved)] (2025)
 [[Category:Oolite Development]]

@@ Line 60: / Line 60: @@
 * The modern (v2) ABI, which provides richer reflection metadata, smaller binaries and reduced memory usage. This is selected with the <code>-fobjc-runtime=gnustep-2.0</code> flag in Clang 7.0 or later.
-Note that currently there is a [https://github.com/gnustep/libobjc2/issues/357 linking error] when trying to build Oolite using the supported ABI 2.2. On Windows MinGW64, there are unfortunately issues that prevent building GNUStep Base with ABI 1.9. Curiously, compiling with the following (still using Clang) but leaving the ABI as 1.9 in Oolite's GNUmakefile also worked possibly opening up a way to get Clang working on MinGW64:
+Note that currently there is a [https://github.com/gnustep/libobjc2/issues/357 linking error] when trying to build Oolite using the supported ABI 2.2. On Windows MinGW64, there are unfortunately issues that prevent building GNUStep Base with ABI 1.9. Curiously, compiling with the following (still using Clang) but leaving the ABI as 1.9 in Oolite's GNUmakefile also worked:
   ./configure --prefix=/usr --with-library-combo=gnu-gnu-gnu --with-libdir=lib --with-objc-lib-flag="-L/usr/lib/x86_64-linux-gnu/ -lobjc"
-ABI 1.9 is unsupported so GNUStep developers do not offer assistance or bug fixes for it. Hence even if it were possible to get it to work on all platforms, it would probably be inadvisable to switch Oolite to use Clang ABI 1.9.
+Clang ABI 1.9 only works with Oolite on Linux not MinGW64. ABI 1.9 is unsupported so GNUStep developers do not offer assistance or bug fixes for it. Hence even if it were possible to get it to work on all platforms, it would probably be inadvisable to switch Oolite to use Clang ABI 1.9.
 == Links ==

← Older revision		Revision as of 13:15, 28 October 2025
Line 65:		Line 65:

	ABI 1.9 is unsupported so GNUStep developers do not offer assistance or bug fixes for it. Hence even if it were possible to get it to work on all platforms, it would probably be inadvisable to switch Oolite to use Clang ABI 1.9.		ABI 1.9 is unsupported so GNUStep developers do not offer assistance or bug fixes for it. Hence even if it were possible to get it to work on all platforms, it would probably be inadvisable to switch Oolite to use Clang ABI 1.9.
		+
		+	== Links ==
		+	*[https://bb.oolite.space/viewtopic.php?t=21898 BB thread: Clang build ABI 1.9 (+latest gnustep-base) (solved)] (2025)

	[[Category:Oolite Development]]		[[Category:Oolite Development]]

← Older revision		Revision as of 13:10, 28 October 2025
Line 65:		Line 65:

	ABI 1.9 is unsupported so GNUStep developers do not offer assistance or bug fixes for it. Hence even if it were possible to get it to work on all platforms, it would probably be inadvisable to switch Oolite to use Clang ABI 1.9.		ABI 1.9 is unsupported so GNUStep developers do not offer assistance or bug fixes for it. Hence even if it were possible to get it to work on all platforms, it would probably be inadvisable to switch Oolite to use Clang ABI 1.9.
		+
		+	[[Category:Oolite Development]]

← Older revision		Revision as of 01:02, 28 October 2025
Line 60:		Line 60:
	* The modern (v2) ABI, which provides richer reflection metadata, smaller binaries and reduced memory usage. This is selected with the <code>-fobjc-runtime=gnustep-2.0</code> flag in Clang 7.0 or later.		* The modern (v2) ABI, which provides richer reflection metadata, smaller binaries and reduced memory usage. This is selected with the <code>-fobjc-runtime=gnustep-2.0</code> flag in Clang 7.0 or later.

−	Note that currently there is a [https://github.com/gnustep/libobjc2/issues/357 linking error] when trying to build Oolite using the supported ABI 2.2. On Windows MinGW64, there are unfortunately issues that prevent building GNUStep Base with ABI 1.9. ABI 1.9 is unsupported so GNUStep developers do not offer assistance or bug fixes for it. Hence even if it were possible to get it to work on all platforms, it would be inadvisable to switch Oolite to use Clang ABI 1.9.	+	Note that currently there is a [https://github.com/gnustep/libobjc2/issues/357 linking error] when trying to build Oolite using the supported ABI 2.2. On Windows MinGW64, there are unfortunately issues that prevent building GNUStep Base with ABI 1.9. Curiously, compiling with the following but leaving the ABI as 1.9 in Oolite's GNUmakefile also worked possibly opening up a way to get Clang working on MinGW64:
		+
		+	./configure --prefix=/usr --with-library-combo=gnu-gnu-gnu --with-libdir=lib --with-objc-lib-flag="-L/usr/lib/x86_64-linux-gnu/ -lobjc"
		+
		+	ABI 1.9 is unsupported so GNUStep developers do not offer assistance or bug fixes for it. Hence even if it were possible to get it to work on all platforms, it would probably be inadvisable to switch Oolite to use Clang ABI 1.9.

← Older revision		Revision as of 23:10, 27 October 2025
Line 60:		Line 60:
	* The modern (v2) ABI, which provides richer reflection metadata, smaller binaries and reduced memory usage. This is selected with the <code>-fobjc-runtime=gnustep-2.0</code> flag in Clang 7.0 or later.		* The modern (v2) ABI, which provides richer reflection metadata, smaller binaries and reduced memory usage. This is selected with the <code>-fobjc-runtime=gnustep-2.0</code> flag in Clang 7.0 or later.

−	Note that currently there is a [https://github.com/gnustep/libobjc2/issues/357 linking error] when trying to build Oolite using the supported ABI 2.2. On Windows MinGW64, there are unfortunately issues that prevent building GNUStep Base with ABI 1.9. ABI 1.9 is ~~not a supported~~ GNUStep ~~ABI so their~~ developers do not offer assistance or bug fixes for ~~this 1.9~~. Hence even if it were possible to get it to work on all platforms, it would be inadvisable to switch Oolite to use Clang ABI 1.9.	+	Note that currently there is a [https://github.com/gnustep/libobjc2/issues/357 linking error] when trying to build Oolite using the supported ABI 2.2. On Windows MinGW64, there are unfortunately issues that prevent building GNUStep Base with ABI 1.9. ABI 1.9 is unsupported so GNUStep developers do not offer assistance or bug fixes for it. Hence even if it were possible to get it to work on all platforms, it would be inadvisable to switch Oolite to use Clang ABI 1.9.

@@ Line 1: / Line 1: @@
-This article describes how to build Oolite from source using Clang instead of gcc.
+This article describes how to build Oolite from source using Clang instead of gcc on Linux.
-Open a shell. To force building with Clang for all subsequent commands in your shell, you need to create environment variables for CC and CXX that point to clang. For Linux, it is like this:
+The following lines must be run inside a shell. They are set up for Ubuntu flavours, but can be adapted for other Linux distributions.
   export CC=/usr/bin/clang
   export CXX=/usr/bin/clang++
-Then build the latest release of ''libobjc2'' ([https://github.com/gnustep/libobjc2/releases/tag/v2.2.1 2.2.1] at time of writing) from source as described [https://github.com/gnustep/libobjc2/blob/master/INSTALL here].
+ cd libobjc2
-Then build the latest release of ''gnustep-base'' ([https://github.com/gnustep/libs-base/releases/tag/base-1_31_1 1.31.1] at time of writing) from source as described [https://github.com/gnustep/libs-base/blob/master/INSTALL here].
+ cd tools-make
-A compiler flag required when building Oolite with Clang is directly in Oolite's ''GNUmakefile'' (and so doesn't need to be added manually as used to be necessary). You can see the flag if you open a text editor and load ''GNUmakefile''. There is a line that looks like this:
+ cd libs-base
   ADDITIONAL_OBJCFLAGS += -fobjc-runtime=gnustep-1.9
@@ Line 33: / Line 59: @@
 * The initial GNUstep non-fragile ABI, which was intended to be compatible with the GCC ABI, but provide support for modern Objective-C features. This can be selected with the <code>-fobjc-runtime=gnustep-1.9</code> flag in Clang.
 * The modern (v2) ABI, which provides richer reflection metadata, smaller binaries and reduced memory usage. This is selected with the <code>-fobjc-runtime=gnustep-2.0</code> flag in Clang 7.0 or later.

@@ Line 10: / Line 10: @@
 Then build the latest release of ''gnustep-base'' ([https://github.com/gnustep/libs-base/releases/tag/base-1_31_1 1.31.1] at time of writing) from source as described [https://github.com/gnustep/libs-base/blob/master/INSTALL here].
-Open a text editor and load Oolite's ''GNUmakefile''. Look for the line:
+A compiler flag required when building Oolite with Clang is directly in Oolite's ''GNUmakefile'' (and so doesn't need to be added manually as used to be necessary). You can see the flag if you open a text editor and load ''GNUmakefile''. There is a line that looks like this:
   ADDITIONAL_OBJCFLAGS += -fobjc-runtime=gnustep-1.9
 Now you can build Oolite in the usual way eg. for Linux:
@@ Line 25: / Line 19: @@
   make -f Makefile release-deployment -j$(nproc)
-You can force the use of the Clang/LLVM linker ldd instead of GNU's ld by adding this line to ''GNUmakefile'':
+You can force the use of the Clang/LLVM linker ldd instead of GNU's ld by adding this line to ''GNUmakefile'' next to the line with <code>-fobjc-runtime=gnustep-1.9</code> in it:
   ADDITIONAL_LDFLAGS += -fuse-ld=lld