Lines Matching full:dll
178 When creating a \s-1DLL\s0, along with the source for the \s-1DLL\s0, it is necessary
183 exported from the \s-1DLL\s0, which functions the \s-1DLL\s0 imports, and so on. This
190 In order to mark a function as being exported from a \s-1DLL\s0, it needs to
202 The second file needed for \s-1DLL\s0 creation is an exports file. This file
203 is linked with the object files that make up the body of the \s-1DLL\s0 and it
204 handles the interface between the \s-1DLL\s0 and the outside world. This is a
208 The third file needed for \s-1DLL\s0 creation is the library file that programs
209 will link with in order to access the functions in the \s-1DLL\s0 (an `import
215 a program to link to the dll only as soon as an imported function is
230 Here is an example of creating a \s-1DLL\s0 from a source file \fBdll.c\fR and
232 that uses that \s-1DLL:\s0
235 \& gcc \-c dll.c
236 \& dlltool \-e exports.o \-l dll.lib dll.o
237 \& gcc dll.o exports.o \-o dll.dll
238 \& gcc program.o dll.lib \-o program
242 to determine the name of the \s-1DLL\s0 to which it is associated. See the
342 .IP "\fB\-\-dll\-name\fR \fIname\fR" 4
343 .IX Item "--dll-name name"
346 the \s-1DLL\s0 when the \fB\-e\fR option is used. If this option is not
348 used as the name of the \s-1DLL\s0.
359 contents of the \s-1DLL\s0 are actually encode using Thumb instructions.
394 function in a \s-1DLL\s0, other than by name.
410 Causes \fBdlltool\fR to create external aliases for all \s-1DLL\s0
445 of the associated \s-1DLL\s0(s). This can be performed in addition to any
453 more than one \s-1DLL\s0.
