Important Notice

The pages on this site contain documentation for very old MS-DOS software, purely for historical purposes. If you're looking for up-to-date documentation, particularly for programming, you should not rely on the information found here, as it will be woefully out of date.

                                             ◄Up► ◄Contents► ◄Index► ◄Back►
─────Using ILINK in the Development Process─────────────────────────────────
 
     As you develop your program or dynamic-link library, use ILINK and
     LINK as follows:
 
       1. Use the full linker (LINK) during early stages of
          development. ILINK offers no speed advantage over LINK until
          you have a number of different code and data modules.
 
       2. Prepare for incremental linking as your program grows by
          using the following LINK options:
 
          ◄Prepare for ILINK (/INC)► (in LINK Help)
          ◄Pad Code Segments (/PADC)► (in LINK Help)
          ◄Pad Data Segments (/PADD)► (in LINK Help)
 
       3. Incrementally link with ILINK after you make any small
          changes in your source files.
 
       4. Use LINK for a full link after you make any major changes.
          Major changes include:
 
             ■ Adding a new module
 
             ■ Changing a module's size significantly
 
             ■ Redefining symbols that are shared between modules
 
             ■ Changing a library file used in linking
 
       5. Repeat steps 3 and 4 as necessary.
 
     You may want to use the NMAKE utility to run ILINK and LINK. For
     example, the following description file (read by NMAKE) attempts
     to incrementally link a program, but resorts to a full link if
     incremental linking fails:
 
          PETS.EXE : DOG.OBJ CAT.OBJ BIRD.OBJ
               ILINK /E "LINK /INCR @PETS.LNK" PETS
 
     See: ◄What Is NMAKE?► (in NMAKE Help)
                                    -♦-