Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month! Blinker 5.10 Online Reference - <b> executing blinker from the dos command line</b> [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
 Executing Blinker from the DOS command line
 Blinker, like most other linkers, may be invoked from the DOS prompt with a
 command line specifying the files and commands required to link a program.
 The most basic method of invoking Blinker is by typing:


 at the DOS prompt, where FILE tells Blinker that what follows is one or more
 object files to be linked. In this case TEST is the name of the only file
 (the extension .OBJ is assumed by default).
 This can be expanded upon to include various other commands such as:


 where LIB tells Blinker that what follows is one or more libraries to be
 linked in with the program. In this case MYLIB.LIB and COMPILIB.LIB are the
 libraries (the extension .LIB is assumed), and specifying NOBELL instructs
 Blinker not to sound a beep when the link has been completed.
 Many Blinker commands start with the word "BLINKER", which sometimes means
 that the word "BLINKER" appears to be repeated at the DOS prompt:


 Here the first "BLINKER" executes the BLINKER.EXE and the following "BLINKER
 INCREMENTAL OFF" is a single Blinker command, turning off incremental
 linking. The command FILE includes the TEST.OBJ file in the program.

 Note that a few Blinker commands cannot be used from the command line, and
 must be placed within a link script file, (e.g. BEGINAREA / ENDAREA).

 Blinker commands containing special characters or DOS delimiters should not
 be used from the command line. For instance, the BLINKER DEMONSTRATION DATE
 command requires slashes in its syntax, but because slashes are parsed
 entirely differently by the DOS command interpreter, syntax errors or
 unexpected behavior might result.

Online resources provided by: --- NG 2 HTML conversion by Dave Pearson