🚀 go-pugleaf

In article <1992Oct04.234736.7949@r-node.gts.org> tcomsing@chasm.scar.utoronto.ca writes:
>I recently installed GNU C 2.2.2 and find one thing annoying about it.  That
>being, LINK386 must be run on the OBJect files.  As such, I am attempting to
>write a REXX "program" to automate this process, but I cannot find, no
>matter how hard I look, any kind of documentation for LINK386.

It's in the OS/2 2.0 Toolkit.  There is no documentation supplied with
the OS.  As far as I can tell, LINK.EXE and LINK386.EXE are supplied
as a courtessey.

>I would like to have my REXX "program" execute LINK386 without having
>LINK386 prompt the user for any additional information.

Just provide all the parameters on the command line.  You know how you
get prompted when you type LINK386 with no parameters?  Well, supply
the parameters on the command line, separated by commas, in the same
order the program asks you for them.  Terminate the command line with
a semicolon.

Type LINK386 /? for a brief summary.  It should be enough.

>Also, after LINK386 is run, I get a warning similar to the following:
>L4071: no pmtype specified; assuming WINDOWCOMPAT

You can ignore this if your program is intended to run in a text window.

>Can someone tell me what are valid options to use with the /PMTYPE switch?

WINDOWCOMPAT    - will run in a text window
NONWINDOWCOMPAT - will only run in a full-screen session
WINDOWAPI       - a PM program

Note that you can specify this information in the app's .DEF file as
well.  This is the recommended place for definitions that go into the
.EXE header (like the pmtype).  See almost any OS/2 programming book
for information on .DEF files.
-- 
David Charlap         |"there aren't 50,000 things for which it's worth writing
dic5340@hertz.njit.edu| software; and the computer industry doesn't have enough
----------------------+ programmers to create that much good software.
Therefore, most of it must be worthless" -- Boris Beizer "The Frozen Keyboard"