Lines Matching full:dll
166 When creating a \s-1DLL\s0, along with the source for the \s-1DLL\s0, it is necessary
171 exported from the \s-1DLL\s0, which functions the \s-1DLL\s0 imports, and so on. This
178 In order to mark a function as being exported from a \s-1DLL\s0, it needs to
192 The second file needed for \s-1DLL\s0 creation is an exports file. This file
193 is linked with the object files that make up the body of the \s-1DLL\s0 and it
194 handles the interface between the \s-1DLL\s0 and the outside world. This is a
198 The third file needed for \s-1DLL\s0 creation is the library file that programs
199 will link with in order to access the functions in the \s-1DLL\s0. This file
213 Here is an example of creating a \s-1DLL\s0 from a source file \fBdll.c\fR and
215 that uses that \s-1DLL:\s0
218 \& gcc \-c dll.c
219 \& dlltool \-e exports.o \-l dll.lib dll.o
220 \& gcc dll.o exports.o \-o dll.dll
221 \& gcc program.o dll.lib \-o program
314 .IP "\fB\-\-dll\-name\fR \fIname\fR" 4
315 .IX Item "--dll-name name"
318 the \s-1DLL\s0 when the \fB\-e\fR option is used. If this option is not
320 used as the name of the \s-1DLL\s0.
331 contents of the \s-1DLL\s0 are actually encode using Thumb instructions.
366 function in a \s-1DLL\s0, other than by name.
382 Causes \fBdlltool\fR to create external aliases for all \s-1DLL\s0
