Changes between Version 9 and Version 10 of PortingTips

Timestamp:

Nov 28, 2016, 12:17:31 AM (8 years ago)

Author:

dmik

Comment:

Add OS/2 specific build details to Autoconf-based packages

PortingTips

@@ -28 +28 @@
 
 With the latest `libtool` it is possible to have a buildlevel string built into a dll. To do so you need to teach the `Makefile` how to handle it. Most likely it is the best practice to change `Makefile.am` and then do a `sh -c "autoreconf -fvi"`. How to adjust a `Makefile.am` can be seen here: r1823 
+
+=== Add OS/2 specific build details to Autoconf-based packages ===
+
+**Method 1**. If `configure.ac` already uses AC_CANONICAL_TARGET or AC_CANONICAL_HOST macros, then you can add the following excerpt to it to do OS/2-specific job (`$target_os` becomes `$host_os` if AC_CANONICAL_HOST is used instead of AC_CANONICAL_TARGET):
+
+{{{
+case "$host_os" in
+os2*)
+        # Increase stack size to 8MB
+        export LDFLAGS="$LDFLAGS -Zstack 0x2000"
+esac
+}}}
+
+**Method 2**. If the above AC_CANONICAL macros are not used, then it will be simpler to use `uname` to do the OS/2-specific job:
+
+{{{
+case `uname -s 2>/dev/null` in
+OS/2)
+        # Increase stack size to 8MB
+        export LDFLAGS="$LDFLAGS -Zstack 0x2000"
+esac
+}}}
+
+Note though that if you need to add such a block more than once, it makes sense to add AC_CANONICAL_TARGET right after AC_INIT to `configure.ac` and go with //Method 1// described above.