Changes between Version 1 and Version 2 of kOptions


Ignore:
Timestamp:
May 16, 2007, 11:25:25 AM (18 years ago)
Author:
guest
Comment:

Added some (hopefully correct) details about wildcard handling

Legend:

Unmodified
Added
Removed
Modified

  • kOptions

    v1 v2  
    1111
    1212These are mentioned in '''ReleaseNotes.os2''' but not sure what they do exactly:
    13   * -Zargs-wild: something with wildcards?
     13  * -Zargs-wild: something with wildcards - call _wildcard (see below) automatically on startup?
    1414  * -Zargs-resp: ??
    1515  * -Zdll-search: ??
    … …  
    2828  * -Zstack: set the stack size
    2929  * -Zso: create stand-alone DLL
    30   * -Zsys: create stand-alone OS/2 program (no emx.dll)
     30  * -Zsys: create stand-alone OS/2 program (no emx.dll) - there's nothing similar for
     31                current libc, if you use new gcc with new libc, you always need the libcxxx.dll
    3132  * -Zsysv-signals: select the `System V' signal processing model
     33
     34Finally, there are a couple of special functions which simplify porting of Unix programs:
     35 * _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. BTW, is there code to try and detect the calling shell, to avoid double expansion when a unix shell is used? I seem to remember that EMX did something like that?