Changes between Version 4 and Version 5 of kOptions


Ignore:
Timestamp:
Aug 1, 2007, 4:44:56 AM (12 years ago)
Author:
guest
Comment:

Fixups and additions by Dave Yeo

Legend:

Unmodified
Added
Removed
Modified
  • kOptions

    v4 v5  
    1 GCC on OS/2 supports several extra options. They all start with -Z. With the exception of -Zomf (others?) they are affecting the linking.
     1GCC on OS/2 supports several extra options. Most start with -Z. With the exception of -Zomf (others?) they are affecting the linking.
    22
    33  * -Zcrtdll: link the C library dynamically
     
    88  * -Zmap: tell linker or emxbind to create a .map file that contains the addresses   of all symbols
    99  * -Zno-autoconv: switch off automatic conversion between a.out and OMF format when linking.
     10  * -Zautoconv: switch on automatic conversion between a.out and OMF format when linking.
    1011  * -Zomf: compile and link using OMF format instead of a.out.
    1112  * -Zargs-wild: call {{{_wildcard()}}} (see below) automatically on startup
     13  * -Zdll-search: Enables dlls as valid libraries. (default disabled)
     14  * -Zsym: Invoke mapsym.cmd on the mapfile to produce a .sym file. Requires -Zmap
     15These may not be OS/2 specific
     16  * -Bstatic, -non_shared, -dn, -static: Link with static libraries.
     17  * -Bshared, -call_shared, -dy: Link with shared libraries. (default)
    1218
    1319These are mentioned in '''ReleaseNotes.os2''' but not sure what they do exactly:
    1420  * -Zargs-resp: ??
    15   * -Zdll-search: ??
    1621  * -Zhigh-low: ??
    1722  * -Zno-fork: turn off the {{{fork()}}} function?
     
    3136  * -Zsysv-signals: select the `System V' signal processing model
    3237
     38There are also various environmental variables that affect the linker type.
     39(from the output of emxomfld 0.6.3)
     40
     41Environment variables:
     42  EMXOMFLD_TYPE:
     43    The type of linker we're using. Values: WLINK, VAC365, VAC308, LINK386.
     44        WLINK    wlink.exe from Open Watcom v1.5 or later.
     45        VAC365   ilink.exe from IBM C and C++ Compilers for OS/2 v3.6 or later.
     46        VAC308   ilink.exe from Visual Age for C++ v3.08.
     47        LINK386  link386 form OS/2 install or DDK.
     48  EMXOMFLD_LINKER:
     49    Name of the linker to use and optionally extra parameters. Spaces in the
     50    linker name or path is not supported. Quotes are not supported either.
     51The default values for these two variables are VAC365 and ilink.exe.
     52  EMXOMFLD_RC_TYPE:
     53    The type of resource compiler we're using. Values: RC,WRC.
     54        RC       rc.exe as shipped with OS/2 or found in the Toolkit
     55        WRC      wrc.exe from Open Watcom v1.6 or later.
     56  EMXOMFLD_RC:
     57    Name of the resource compiler to use and optionally extra parameters.
     58    Spaces or quotes in the name or path are not supported.
     59The default values for these two variables are RC and rc.exe.
     60 
    3361Finally, there are a couple of special functions which simplify porting of Unix programs:
    3462 * {{{_wildcard (int *argc, char ***argv)}}}: Same as in EMX, i.e. it expands it's arguments like a unix shell would do (but OS/2 cmd.exe doesn't), so you typically want to use this when porting a unix command line application. Instead of adding this to a program, compilation with -Zargs-wild can be used.