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

/ql                     Perform QuickLinker link
---------------------------------------------------------------------------------

 Description:

 This option creates a file with the extension .QLK.  The file contains
 information about the library modules linked into the program.

 The first use of /ql will create a .QLK file, causing a slightly slower
 link.  Subsequent links will use the existing .QLK file to locate needed
 library modules and should link faster.  It is legitimate to alternate
 linking with and without using /ql.  The .QLK file will only be accessed
 (or created) when /ql is specified, otherwise the link proceeds normally.

 Use of /ql presumes that you will not change your libraries (count, order,
 and version) between links.  Therefore, it is not recommended that you use
 /ql if you change libraries frequently. If you do change your library setup, delete the old .QLK file or else you may receive internal
 errors from WarpLink when using the /ql option as it tries to use old,
 invalid, library information.

 With direct library module specification, the speed increase gained by
 using /ql can be simply breathtaking.  Depending upon the number of
 libraries and modules specified, you may see the link speed increase up
 to three times the normal link speed. The more library modules specified,
 the greater the increase in speed by using /ql.  Without direct library
 module specification, speed increases are more modest, typically 10%-40%
 increase in link speed. Programs with several large libraries will benefit
 the most from using the /ql option.

 If your program links in new library modules, your .QLK file will lose
 efficiency over time because it appends the new library module
 information at the end of the file, and causes more passes than a
 standard link.  Also, old library modules that are no longer used will
 continue to be linked, causing increased memory overhead.  To remedy
 either of these conditions, simply delete the .QLK file and use the /ql
 option to build a new file containing your new library use structure.

 .QLK files are deleted on linker error or Control-C exit if WarpLink is
 actively writing to them, rather than passively reading them.  If you
 interrupt linking during the creation of a .QLK file so that it is not
 completely built, the .QLK file will be automatically deleted by
 WarpLink to prevent subsequent use of the incomplete .QLK file. 
 Interruption during read access of a pre-existing .QLK file does not
 delete the .QLK file.
 If you use the /ql option with direct library module specification, you
 must place the option before the library list in the link file.  If these
 options are not placed before the library list, you will receive internal
 errors due to irreversible processing of the library modules that requires
 those options not be altered after libraries are processed.  For example,
 these options execute successfully:

 WARPLINK /QL /OP:M /R OBJMODULE,EXENAME,,LIB1:MOD1 LIB2

 Do not place the /ql option after the library list as follows:

 WARPLINK /OP:M /R OBJMODULE,EXENAME,,LIB1:MOD1 LIB2 /QL

 If you experience internal errors, unresolved external warning messages,
 or linking of unwanted library modules when using /ql, delete the old
 .QLK file and relink using the /ql option.