WLink: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
Content added Content deleted
m (Added link) |
(added the MZ and .COM mention) |
||
| Line 4: | Line 4: | ||
** Supports range of input formats, OMF/OBJ, Win32/COFF, ELF |
** Supports range of input formats, OMF/OBJ, Win32/COFF, ELF |
||
** Supports library files |
** Supports library files |
||
** Supports many output file formats from EXE, LE, Win32/PE, Novell NLM files, Pharlap files, QNX, OS2, etc. |
** Supports many output file formats from EXE, LE, Win32/PE, Novell NLM files, Pharlap files, QNX, OS2, etc. It even supports MZ and .COM |
||
** Handles setting code offset address |
** Handles setting code offset address |
||
** Supports Watcom, Codeview and Dward debugging information |
** Supports Watcom, Codeview and Dward debugging information |
||
Revision as of 13:13, 1 March 2012
WLink is the linker that comes with Watcom C/C++. Supports a wide range of options and is flexible to a degree. The only problem is that Watcom just uses the virtual address entries of the ELF format, which can be specified at link time with the offset=0x???????? directive.
- Pros
- Supports range of input formats, OMF/OBJ, Win32/COFF, ELF
- Supports library files
- Supports many output file formats from EXE, LE, Win32/PE, Novell NLM files, Pharlap files, QNX, OS2, etc. It even supports MZ and .COM
- Handles setting code offset address
- Supports Watcom, Codeview and Dward debugging information
- Supports flat binary files
- Custom segment location