ldformat.gml

开放源码的编译器open watcom 1.6.0版的源代码

"TERMGLOBAL" is assumed.
.np
If "PM" is specified, a Presentation Manager application will be
created.
The application uses the API provided by the Presentation Manager and
must be executed in the Presentation Manager environment.
.np
lf "PMCOMPATIBLE" (short form "PMC") is specified, an application
compatible with Presentation Manager will be created.
The application can run inside the Presentation Manager or it can run
in a separate screen group.
An application can be of this type if it uses the proper subset of
OS/2 video, keyboard, and mouse functions supported in the
Presentation Manager applications.
This is the default.
.np
If "FULLSCREEN" (short form "FULL") is specified, an OS/2 full screen
application will be created.
The application will run in a separate screen group from the
Presentation Manager.
.np
If "PHYSDEVICE" (short form "PHYS") is specified, the executable file
is marked as a physical device driver.
.np
If "VIRTDEVICE" (short form "VIRT") is specified, the executable file
is marked as a virtual device driver.
.if '&target' ne 'QNX' .do begin
.np
For more information on OS/2 executable file formats,
see the chapter entitled :HDREF refid='os2chap'..
.do end
.mnote PHARLAP
(short form "PHAR") tells the &lnkname to generate an executable file
that will run under Phar Lap's 386|DOS-Extender.
.np
There are 4 forms of executable files:
simple, extended, relocatable and segmented.
If "EXTENDED" (short form "EXT") is specified, an extended form of the
executable file with file extension "exp" will be generated.
If "REX" is specified, a relocatable executable file with file
extension "rex" will be generated.
If "SEGMENTED" (short form "SEG") is specified, a segmented executable
file with file extension "exp" will be generated.
If neither "EXTENDED", "REX" or "SEGMENTED" is specified, a simple
executable file with file extension "exp" will be generated.
Note that the default file extensions can be overridden by using the
"NAME" directive to name the executable file.
.np
The simple form is for flat model 386 applications.
It is the only format that can be loaded by earlier versions of
386|DOS-Extender (earlier than 1.2).
.np
The extended form is used for flat model applications that have been
linked in a way which requires a method of specifying more information
for 386|DOS-Extender than possible with the simple form.
.np
The relocatable form is similar to the simple form.
Unique to the relocatable form is an offset relocation table.
This allows the loader to load the program at any location it chooses.
.np
The segmented form is used for embedded system applications like
Intel RMX.
These executables cannot be loaded by 386|DOS-Extender.
.np
A simple form of the executable file is generated in all but the
following cases.
.autonote
.note
"EXTENDED" is specified in the "FORMAT" directive.
.note
The "RUNTIME" directive is specified.
Options specified by the "RUNTIME" directive can only be specified in
the extended form of the executable file.
.note
The "OFFSET" option is specified.
The value specified in the "OFFSET" option can only be specified in
the extended form of the executable file.
.note
"REX" is specified in the "FORMAT" directive.
In this case, the relocatable form will be generated.
You must not specify the "RUNTIME" directive or the "OFFSET" option
when generating the relocatable form.
.note
"SEGMENTED" is specified in the "FORMAT" directive.
In this case, the segmented form will be generated.
.endnote
.if '&target' ne 'QNX' .do begin
.np
For more information on Phar Lap executable file formats,
see the chapter entitled :HDREF refid='phrchap'..
.do end
.mnote NOVELL
(short form "NOV") tells the &lnkname to generate a NetWare
executable file, more commonly called a NetWare Loadable Module (NLM).
.np
NLMs are further classified according to their function.
The executable file will have a file extension that depends on the
class of the NLM being generated.
The following describes the classification of NLMs.
.begpoint
.point LAN
instructs the &lnkname to generate a LAN driver.
A LAN driver is a device driver for Local Area Network hardware.
A file extension of "lan" is used for the name of the executable file.
.point DSK
instructs the &lnkname to generate a disk driver.
A file extension of "dsk" is used for the name of the executable file.
.point NAM
instructs the &lnkname to generate a file system name-space support
module.
A file extension of "nam" is used for the name of the executable file.
.point MSL
instructs the &lnkname to generate a Mirrored Server Link module. The
default file extension is "msl"
.point CDM
instructs the &lnkname to generate a Custom Device module. The
default file extension is "cdm"
.point HAM
instructs the &lnkname to generate a Host Adapter module. The
default file extension is "ham"
.point NLM
instructs the &lnkname to generate a utility or server application.
This is the default.
A file extension of "nlm" is used for the name of the executable file.
.point 'number'
instructs the &lnkname to generate a specific type of NLM using 'number'.
This is a 32 bit value that corresponds to Novell allocated NLM types.
.np
These are the current defined values:
.begpoint
.point 0 
Specifies a standard NLM (default extension .NLM)
.point 1
Specifies a disk driver module (default extension .DSK)
.point 2 
Specifies a namespace driver module (default extension .NAM)
.point 3 
Specifies a LAN driver module (default extension .LAN)
.point 4
Specifies a utility NLM (default extension .NLM)
.point 5
Specifies a Mirrored Server Link module (default .MSL)
.point 6
Specifies an Operating System module (default .NLM)
.point 7
Specifies a Page High OS module (default .NLM)
.point 8
Specifies a Host Adapter module (default .HAM)
.point 9
Specifies a Custom Device module (default .CDM)
.point 10
Reserved for Novell usage
.point 11
Reserved for Novell usage
.point 12
Specifies a Ghost module (default .NLM)
.point 13
Specifies an SMP driver module (default .NLM)
.point 14
Specifies a NIOS module (default .NLM)
.point 15
Specifies a CIOS CAD type module (default .NLM)
.point 16
Specifies a CIOS CLS type module (default .NLM)
.point 21
Reserved for Novell NICI usage
.point 22
Reserved for Novell NICI usage
.point 23
Reserved for Novell NICI usage
.point 24
Reserved for Novell NICI usage
.point 25
Reserved for Novell NICI usage
.point 26
Reserved for Novell NICI usage
.point 27
Reserved for Novell NICI usage
.point 28
Reserved for Novell NICI usage
.endpoint
.point description
is a textual description of the program being linked.
.endpoint
.if '&target' ne 'QNX' .do begin
.np
For more information on NetWare executable file formats,
see the chapter entitled :HDREF refid='novchap'..
.do end
.mnote QNX
tells the &lnkname to generate a QNX executable file.
.np
If "FLAT" (short form "FL") is specified, a 32-bit flat executable
file is generated.
.np
Under QNX, no file extension is added to the executable file name.
.np
Under other operating systems, the name of the executable file will
have the extension "qnx".
Note that this default extension can be overridden by using the "NAME"
directive to name the executable file.
.np
For more information on QNX executable file formats,
see the chapter entitled :HDREF refid='qnxchap'..
.mnote ELF
tells the &lnkname to generate an ELF format executable file.
.np
ELF format DLLs can also be created.
.if '&target' ne 'QNX' .do begin
.np
For more information on ELF executable file formats,
see the chapter entitled :HDREF refid='elfchap'..
.do end
.esynote
.np
If no "FORMAT" directive is specified, the executable file format will
be selected for each of the following host systems in the way
described.
.begnote
.note DOS
If 16-bit object files are encountered, a 16-bit DOS executable will
be created.
If 32-bit object files are encountered, a 32-bit DOS/4G executable
will be created.
.note OS/2
If 16-bit object files are encountered, a 16-bit OS/2 executable will
be created.
If 32-bit object files are encountered, a 32-bit OS/2 executable will
be created.
.note QNX
If 16-bit object files are encountered, a 16-bit QNX executable will
be created.
If 32-bit object files are encountered, a 32-bit QNX executable will
be created.
.note Windows NT
If 16-bit object files are encountered, a 16-bit Windows executable
will be created.
If 32-bit object files are encountered, a 32-bit Win32 executable will
be created.
.note Windows 95
If 16-bit object files are encountered, a 16-bit Windows executable
will be created.
If 32-bit object files are encountered, a 32-bit Win32 executable will
be created.
.endnote