Identifying the target platform - Revision history

Cbv: move category

2007-01-16T10:18:50Z

move category

Cbv: /* Using GNUStep-Make's support */ Clean-up

2007-01-04T10:44:49Z

Using GNUStep-Make's support: Clean-up

Cbv: Add to category

2007-01-04T09:53:29Z

Add to category

Cbv: Some additions

2005-11-11T09:59:18Z

Some additions

Comrade: Add "standard" macros and a tip for Makefiles

2005-11-10T20:23:34Z

Add "standard" macros and a tip for Makefiles

New page

A common problem is identifying the target platform at compile-time so that specific code can be used, perhaps to work around a quirk, or to access a non-standard feature of the target platform.

== Standard compiler platform macros ==

The following table is a partial extract of [[http://predef.sourceforge.net/preos.html Pre-defined C/C++ Compiler Macros]], part of a useful resource to compiler macro definitions.

Please update the table carefully with your platform or corrections:

{| border="1" cellpadding="2"
|+Platform macros
|-
! Platform !! Defined macro !! Other notes
|-
! FreeBSD
| __FreeBSD__ || Consider using the BSD macro
|-
! Linux
| linux or __linux ||
|-
! MacOS X
| __MACOSX__ or __APPLE__ ||
|-
! NetBSD
| __NetBSD__ || Consider using the BSD macro
|-
! OpenBSD
| __OpenBSD__ || Consider using the BSD macro
|-
! Solaris
| sun or __sun || SunOS versions < 5 will not have __SVR4 or __svr4__ defined
|-
! Windows
| _WIN32 or __WIN32__ ||
|}

You can use #if wrappers like:

<pre>
#if defined (__FreeBSD__)
...
#elif defined (__linux) || defined (linux)
...
#else
...
#endif
</pre>

== Using GNUStep-Make's support ==

Chris Vetter shared a tip on the use of your GNUmakefile.preamble with the following line:

<pre>
ADDITIONAL_OBJCFLAGS += -D$(GNUSTEP_HOST_OS)
</pre>

and then the #if wrappers will look like:

<pre>
#if defined (freebsd)
...
#elif defined (netbsdelf)
...
#else
...
#endif
</pre>

← Older revision		Revision as of 10:18, 16 January 2007
Line 80:		Line 80:
	It's much better generating an error (as mentioned above) than just assuming your code will work on a different platform. The former will most likely get someone involved in your pet project and have them send in patches for their particular system. The latter will probably just annoy people, especially if your code screws up (on) their system due to differences...		It's much better generating an error (as mentioned above) than just assuming your code will work on a different platform. The former will most likely get someone involved in your pet project and have them send in patches for their particular system. The latter will probably just annoy people, especially if your code screws up (on) their system due to differences...

−	[[Category:~~Snippets~~]]	+	[[Category:Development]]

@@ Line 54: / Line 54: @@
 Chris Vetter shared a tip on the use of your GNUmakefile.preamble with the following line:
-<pre>
+ ADDITIONAL_CPPFLAGS += -D$(GNUSTEP_HOST_OS)
 and then the #if wrappers will look like:
-<pre>
+ #if defined( freebsd )
-#if defined (freebsd)
+ ...
-...
+ #elif defined( netbsdelf )
-#elif defined (netbsdelf)
+ ...
-...
+ #else
-#else
+ ...
-...
+ #endif
-To be on the safe side, you may then want to mix the compiler defaults and GNUsteps definitions. It's also good style to add an error or at least a warning in case a particular platform is not (yet) supported.
+To be on the safe side, you may then want to mix the compiler defaults and GNUstep's definitions. It's also good style to add an error or at least a warning in case a particular platform is not (yet) supported.
   #if defined( freebsd ) || defined( __FreeBSD__ )
@@ Line 87: / Line 78: @@
 Always keep in mind that not everyone is using your preferred platform and that implementations may vary. This is especially true with respect to the implementation and usage of ''/proc'' on Linux as compared to other systems.
-It's much better generating an error (as above) than just assuming you code will work on a different platform. The former will most likely get someone involved in your pet project and have them send in patches for their particular system. The latter will probably just annoy people, especially if your code screws up (on) their system due to differences...
+It's much better generating an error (as mentioned above) than just assuming your code will work on a different platform. The former will most likely get someone involved in your pet project and have them send in patches for their particular system. The latter will probably just annoy people, especially if your code screws up (on) their system due to differences...
 [[Category:Snippets]]

← Older revision		Revision as of 09:53, 4 January 2007
Line 88:		Line 88:

	It's much better generating an error (as above) than just assuming you code will work on a different platform. The former will most likely get someone involved in your pet project and have them send in patches for their particular system. The latter will probably just annoy people, especially if your code screws up (on) their system due to differences...		It's much better generating an error (as above) than just assuming you code will work on a different platform. The former will most likely get someone involved in your pet project and have them send in patches for their particular system. The latter will probably just annoy people, especially if your code screws up (on) their system due to differences...
		+
		+	[[Category:Snippets]]

@@ Line 11: / Line 11: @@
 |-
 ! Platform !! Defined macro !! Other notes
 |-
 ! FreeBSD
@@ Line 16: / Line 19: @@
 |-
 ! Linux
-| linux or __linux ||
+| linux or __linux || I also found LINUX
 |-
 ! MacOS X
@@ Line 33: / Line 36: @@
 | _WIN32 or __WIN32__ ||
 |}
 You can use #if wrappers like:
@@ Line 65: / Line 69: @@
 #endif
 </pre>