In addition to supporting all LINK32 options, ldpli includes the following support for Windows systems:
- Indirect files (@ files).
- The -# option, which echoes the command line used to invoke LINK32. This can also be used to redirect output for later use
in indirect files.
ldpli enhances the default behavior of the following LINK32 options:
- If -out:filename is not specified, ldpli will generate an executable file with an extension
.exe using the basename of the first object file rather than defaulting to
noname.exe.
- If -map is specified without specifying the filename (-map:filename), ldpli will generate a map file with the extension
.map using the basename of the first object file.
If -deb was used on the command line at compilation time for debugging purposes with CodeWatch, -deb must also be supplied
on the command line to ldpli. If using mfplx for both compilation and linking, mfplx will automatically invoke ldpli with
-deb.
Note: If linking using your own shell scripts and/or driving
ld directly, you must change from using
-lmf to use
-lmfpliz (PL/I in Enterprise Developer) or
-lmfpli (Open PL/I).
libespli.so and
libespliz.so are no longer used.