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

Using Command Options
----------------------------------------------------------------------------------------

 Both elective and required modules contained in a .DDL file may be overlaid.
 Overlays are specified in the same way as they are during the normal link 
 process,that is, the object modules or libraries are placed in parentheses.
 This flags to the DDL manager that the modules, if used, will be overlaid.

 When creating a .DDL file with the /ddl option, no .OBJ files need to be 
 listed in the object module list.  This is different from the normal linking
 operation of WarpLink that requires at least one .OBJ file to be listed.  
 Not using .OBJ files allows you to create a .DDL file from only library 
 files.  Creating a .DDL file from only library files is a common occurrence.
 If no .OBJ file is specified, then a .DDL file name must be listed because
 there is no default .DDL file name to generate from the first .OBJ file name.
 The .DDL file name is specified in the same manner as a .EXE file name is
 specified in a normal link: either after the first comma following the
 WarpLink options list or on the first separate line following the options
 list.

 If there are any required modules contained within the .DDL, then a loader
 .EXE file is also created when creating a .DDL file. Be cautious when using
 the /ddl option to avoid inadvertently overwriting a pre-existing .EXE file.
 For example, if you create a CLARION.DDL file using the following command 
 line:

 WARPLINK /DDL CLARION,,,CLARION1 CLARION2

 WarpLink will create two files: CLARION.DDL and CLARION.EXE, by using the
 code in CLARION.OBJ, CLARION1.LIB, and CLARION2 modules.  Any pre-existing
 CLARION.EXE file will be overwritten by this process.  To avoid overwriting
 a pre-existing CLARION.EXE file explicitly, specify a different DDL name 
 (e.g. create a CLAR.DDL and CLAR.EXE file) as follows:

 WARPLINK /DDL CLARION,CLAR,,CLARION1 CLARION2

 Alternatively, you can specify a different directory for the resulting 
 files.

 If there are no required modules within a .DDL file (all are elective) then
 no loader .EXE file is created.