Click above to get retro games delivered to your door ever month!

 Blinker link script files
------------------------------------------------------------------------------
 When using Blinker you will soon find that the 128 character command line
 maximum imposed by the operating system is no longer sufficient to contain
 all of the commands you wish to specify to the linker. This limit can easily
 be overcome by using a link script, which contains all the files and
 commands to be processed by Blinker, removing the need to type them
 repeatedly at the DOS prompt. The script file may be created with any text
 editor or word processor which stores files in ASCII format.

 The link (or script) file usually has the same name as the program being
 created but with a default extension of .LNK. Into this file you then place
 all of the commands, files and libraries that you want Blinker to act upon
 when linking. The online help contains detailed descriptions of all the
 commands which may be used either on the command line or in a script file.
 For example, to create a DOS extended program with Microsoft Visual C++ 1.5,
 the file MYAPP.LNK would contain the following:

 # Set the output .EXE file name
 OUTPUT Myapp
 # Set the stack to 4 Kb
 STACK 4096
 # Create a DOS extended .EXE
 BLINKER EXECUTABLE EXTENDED
 # Start of .OBJ files
 FILE Myapp1
 FILE Myapp2
 FILE Myapp3
 LIB Mylib
 # Always include a replacement library
 SEARCH blxmvc15
 # (Optional) compiler language library
 LIB llibce

 Obviously, typing this amount of information every time you wanted to
 perform a link would be time consuming. Thus, you could execute Blinker
 using the commands in the link file by typing at the DOS prompt:

 BLINKER @Myapp

 Note that the use of the @ symbol informs Blinker that the name of a link
 file follows, so the extension .LNK is assumed.