Tips & Tricks for porting applications: Difference between revisions
No edit summary |
mNo edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== spawn* & exec* considerations == | == spawn* & exec* considerations == | ||
On unix these functions take a shell script *.sh as parameter for the executable. In the OS/2 libc implementation this does not work. You will need to modify the parameter list so that the first entry is the executable for the script. | On unix these functions take a shell script *.sh as parameter for the executable. In the OS/2 libc implementation this does not work. You will need to modify the parameter list so that the first entry is the executable for the script. | ||
* cmd.exe for rexx scripts | * cmd.exe for rexx scripts | ||
* sh.exe for unix shell scripts | * sh.exe for unix shell scripts | ||
One excellent source of tip & tricks is Alexander Mai's [[The un*x to OS/2-EMX Porting FAQ]] | |||
[[Category:Porting Articles]] | |||
Latest revision as of 20:01, 16 January 2017
spawn* & exec* considerations
On unix these functions take a shell script *.sh as parameter for the executable. In the OS/2 libc implementation this does not work. You will need to modify the parameter list so that the first entry is the executable for the script.
- cmd.exe for rexx scripts
- sh.exe for unix shell scripts
One excellent source of tip & tricks is Alexander Mai's The un*x to OS/2-EMX Porting FAQ