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

/clpi                   Use Clipper-specific incremental link
---------------------------------------------------------------------------------

 Users:

 The /clpi option can only be used by Clipper programmers.

 Description:

 Use this option to take advantage of WarpLink's Clipper-specific incremental 
 link capabilities.  Incremental linking is a tool for rapid
 program development.  It will drastically cut down on your linking time
 because only those object files which have been modified since the last
 link will be re-linked.

 Incremental linking is specified using the /clpi option.  During the first
 run of a link using /clpi, a full link is performed and an incremental link
 file is created.  The name of the incremental link file will be the name of
 the executable file, with a .ILF extension.  The .ILF file contains
 information used during later links of the program.  .ILF files must reside
 in the current directory in order for WarpLink to find them.  WarpLink will
 attempt to do an incremental link whenever the /clpi option is used and a 
 .ILF file is present for the program. If no .ILF file is present, a new one
 will be built for use with the next incremental link.

 Incremental linking works only with Clipper .OBJ files.  If you change a
 non-Clipper object module or any library, the incremental link will fail
 and allow you the option of continuing with a full link.  This will create
 a new .ILF file.

 WarpLink bases the decision to modify code using the incremental link upon
 the time and date stamp of a file.  If the date or time stamp of a file has
 not changed since the last incremental link, WarpLink will assume that no
 code changes were made.

 You can change a symbol name, rearrange variables in the symbol table, and
 do some limited addition or deletion of symbol names and still have a
 successful incremental link.  Exceeding the pad length with code changes, 
 adding more than two new symbols, or changing the position of a procedure
 within a symbol table will force the incremental link to fail
 and require a full link.

 It is recommended that you perform a full link without the /clpi option on
 the final version of your software after development is complete. This will
 remove Clipper procedure and symbol table padding that is added during the
 incremental link process.

 Using the /clpi option will add to the size of your .EXE file. WarpLink
 must make allowances for new code in your .EXE file, so it adds some free
 space for later changes.  See the explanation of the /clpp option for more
 complete information on this .EXE file padding.

 The /clpi and /sp options cannot be used together. You can't perform symbol
 compaction on a file that was linked incrementally.  The option specified
 last will be used.

 If you use the /clpi 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 /CLPI /OP:M /R OBJMODULE,EXENAME,,LIB1:MOD1 LIB2

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

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


----------------------------------[ Example ]------------------------------------

 WARPLINK /CLPI /OP:M /R ObjectModule,ExeName,,Library1,Module1,Library2