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

 Using nested link scripts
------------------------------------------------------------------------------
 You will notice on the Blinker distribution disk a number of files with the
 extension .LNK, in other words link files. These have been included to
 simplify the linking process and to take advantage of one of the special
 features of Blinker, namely partial overlaying of libraries using the MODULE
 command.

 The MODULE command extracts individual .OBJ files (or modules) from their
 libraries and forces them either into the root of the program or into the
 overlay area, depending on the location of the MODULE command itself. In
 this way each nested link file can be individually tailored to each program,
 with the user commenting out the modules which are not to be included in the
 root or overlay area.

 It is also a simple matter to create your own nested link scripts to keep
 standard options and libraries in a single place, much the same as with
 libraries of .OBJ files or even #include files at the source level.
 Any of these files may be referenced from your own link files merely by
 preceding the name of the file with the '@' symbol.

 For example, modifying the earlier sample script we could have:

 MYAPP.LNK:
 OUTPUT Myapp
 STACK 4096
 BLINKER EXECUTABLE EXTENDED
 FILE Myapp1
 FILE Myapp2
 FILE Myapp3
 @MSVC       # Reference to a nested link file

 where, in this case, MSVC.LNK is the nested link script.
 This could contain the following commands:

 MSVC.LNK:
 LIB Mylib
 LIB Alib
 LIB Blib
 # Always include a replacement library
 SEARCH blxmvc15
 # (Optional) compiler language library
 LIB llibce

 This allows a developer to keep all utilities and common routines in a
 separate script which can be combined with all of his or her programs.