Changes between Version 8 and Version 9 of kOptions

Timestamp:

Jan 1, 2019, 7:24:30 AM (5 years ago)

Author:

dryeo

Comment:

--

kOptions

@@ -1 +1 @@
 GCC on OS/2 supports several extra options. Most start with -Z. With the exception of -Zomf (others?) they are affecting the linking.
 
-  * -Zcrtdll: link the C library dynamically
-  * -Zdll: create a dynamic link library
-  * -Zexe: create foo which is executable which calls foo.exe which is also created.
-  * -Zhigh-mem: link so that the C library calls in the program make use of "high memory". This is similiar to specifying OBJ_ANY to OS/2 API memory calls. If you use this option you should include os2safe.h as the first include file in every C file that uses OS/2 APIs.
+  * -Zcrtdll: link the C library dynamically. This is the default and while unneeded, doesn't hurt.
+  * -Zdll: create a dynamic link library.
+  * -Zexe: create foo which is executable which calls foo.exe which is also created. Not usually needed as most configure scripts use exeext and OS/2 linkers will create an executable if the target ends with .exe
+  * -Zhigh-mem: link so that the C library calls in the program make use of "high memory". This is similiar to specifying OBJ_ANY to OS/2 API memory calls. If you use this option you should include os2safe.h as the first include file in every C file that uses OS/2 APIs unless you know the calls are high memory safe.
   * -Zlinker: pass option through to linker (like {{{-Zlinker /EXEPACK:2 -Zlinker /PACKCODE}}})
   * -Zmap: tell linker or emxbind to create a .map file that contains the addresses   of all symbols
   * -Zno-autoconv: switch off automatic conversion between a.out and OMF format when linking.
   * -Zautoconv: switch on automatic conversion between a.out and OMF format when linking.
-  * -Zomf: compile and link using OMF format instead of a.out.
+  * -Zomf: compile and/or link using OMF format instead of a.out. kLIBC will link aout object files into an OMF target so only adding -Zomf to LDFLAGS is usually necessary.
   * -Zargs-wild: call {{{_wildcard()}}} (see below) automatically on startup
   * -Zargs-resp: call {{{_reponse()}}} (see below) automatically on startup
-  * -Zbin-files: open files in binary mode by default
+  * -Zbin-files: open files in binary mode by default. Doesn't work 100% of the time.
   * -Zdll-search: Enables dlls as valid libraries. (default disabled)
-  * -Zstack: set the stack size
+  * -Zstack: set the stack size. Specify stack size in kBs. -Zstack 0x2000 will force use of a 8MB stack.
   * -Zsym: Invoke mapsym.cmd on the mapfile to produce a .sym file. Requires -Zmap
-These may not be OS/2 specific
+These are not OS/2 specific
   * -Bstatic, -non_shared, -dn, -static: Link with static libraries.
   * -Bshared, -call_shared, -dy: Link with shared libraries. (default) 
@@ -25 +25 @@
   * -Zno-unix: non-unix like mode, affects slash handling and fork()?
 
-These were supported options with EMX/gcc 2.8.x, not sure if they are still supported now:
-  * -Zbsd-signals: select the `BSD' signal processing model
+These were supported options with EMX/gcc 2.8.x and generally are ignored for compatibility:
+  * -Zbsd-signals: select the `BSD' signal processing model, (now default)
   * -Zmt: multithread code (now default)
   * -Zmtd: multithread code, link C library dynamically
-  * -Zmts: multithread code, link C library statically
+  * -Zmts: multithread code, link C library statically. disabled due to licensing issues.
   * -Zno-rte: create DLL without runtime environment
   * -Zsmall-conv: use small, fast, and inaccurate routines for converting decimal numbers to binary and vice versa