2 .TH WINEBUILD 1 "October 2005" "@PACKAGE_STRING@" "Wine Developers Manual"
4 winebuild \- Wine dll builder
6 .BI winebuild\ [options]\ [input\ files]
9 generates the assembly files that are necessary to build a Wine dll,
10 which is basically a Win32 dll encapsulated inside a Unix library.
13 has different modes, depending on what kind of file it is asked to
14 generate. The mode is specified by one of the mode options specified
15 below. In addition to the mode option, various other command-line
16 option can be specified, as described in the \fBOPTIONS\fR section.
18 You have to specify exactly one of the following options, depending on
19 what you want winebuild to generate.
22 Build an assembly file from a .spec file (see \fBSPEC FILE SYNTAX\fR
23 for details), or from a standard Windows .def file. The .spec/.def
24 file is specified via the -E option. The resulting file must be
25 assembled and linked to the other object files to build a working Wine
26 dll. In this mode, the
28 should be the list of all object files that will be linked into the
31 to get the list of all undefined symbols that need to be imported from
35 Build an assembly file for an executable. This is basically the same as
36 the --dll mode except that it doesn't require a .spec/.def file as input,
37 since an executable need not export functions. Some executables however
38 do export functions, and for those a .spec/.def file can be specified via
39 the -E option. The executable is named from the .spec/.def file name if
40 present, or explicitly through the -F option. The resulting file must be
41 assembled and linked to the other object files to build a working Wine
42 executable, and all the other object files must be listed as
46 Build a .def file from a spec file. The .spec file is specified via the
47 -E option. This is used when building dlls with a PE (Win32) compiler.
50 Build a PE import library from a spec file. The .spec file is
51 specified via the -E option.
54 Generate a .o file containing all the input resources. This is useful
55 when building with a PE compiler, since the PE binutils cannot handle
56 multiple resource files as input. For a standard Unix build, the
57 resource files are automatically included when building the spec file,
58 so there's no need for an intermediate .o file.
61 .BI \--as-cmd= as-command
62 Specify the command to use to compile assembly files; the default is
65 .BI \-b,\ --target= cpu-manufacturer[-kernel]-os
66 Specify the target CPU and platform on which the generated code will
67 be built. The target specification is in the standard autoconf format
68 as returned by config.sub.
70 .BI \-d,\ --delay-lib= name
71 Set the delayed import mode for the specified library, which must be
72 one of the libraries imported with the \fB-l\fR option. Delayed mode
73 means that the library won't be loaded until a function imported from
74 it is actually called.
77 Ignored for compatibility with the C compiler.
79 .BI \-e,\ --entry= function
80 Specify the module entry point function; if not specified, the default
85 for executables (if the standard C
89 is used instead). This is only valid for Win32 modules.
91 .BI \-E,\ --export= filename
92 Specify a .spec file (see \fBSPEC FILE SYNTAX\fR for details),
93 or a standard Windows .def file that defines the exports
94 of the DLL or executable that is being built.
96 .B \--external-symbols
97 Allow linking to external symbols directly from the spec
98 file. Normally symbols exported by a dll have to be defined in the dll
99 itself; this option makes it possible to use symbols defined in
100 another Unix library (for symbols defined in another dll, a
102 specification must be used instead).
105 Specify a code generation option. Currently \fB\-fPIC\fR and
106 \fB\-fasynchronous-unwind-tables\fR are supported. Other options are
107 ignored for compatibility with the C compiler.
110 Create a fake PE module for a dll or exe, instead of the normal
111 assembly or object file. The PE module contains the resources for the
112 module, but no executable code.
114 .BI \-F,\ --filename= filename
115 Set the file name of the module. The default is to use the base name
116 of the spec file (without any extension).
119 Display a usage message and exit.
121 .BI \-H,\ --heap= size
122 Specify the size of the module local heap in bytes (only valid for
123 Win16 modules); default is no local heap.
126 Ignored for compatibility with the C compiler.
129 Remove the stdcall decorations from the symbol names in the
130 generated .def file. Only meaningful in \fB--def\fR mode.
133 Ignored for compatibility with the C compiler.
135 .BI \--large-address-aware
136 Set a flag in the executable to notify the loader that this
137 application supports address spaces larger than 2 gigabytes.
139 .BI \--ld-cmd= ld-command
140 Specify the command to use to link the object files; the default is
143 .BI \-L,\ --library-path= directory
144 Append the specified directory to the list of directories that are
145 searched for import libraries.
147 .BI \-l,\ --library= name
148 Import the specified library, looking for a corresponding
149 \fIlibname.def\fR file in the directories specified with the \fB-L\fR
153 Generate 16-bit, 32-bit, respectively 64-bit code.
155 .BI \-M,\ --main-module= module
156 When building a 16-bit dll, set the name of its 32-bit counterpart to
157 \fImodule\fR. This is used to enforce that the load order for the
158 16-bit dll matches that of the 32-bit one.
160 .BI \-N,\ --dll-name= dllname
161 Set the internal name of the module. It is only used in Win16
162 modules. The default is to use the base name of the spec file (without
163 any extension). This is used for KERNEL, since it lives in
164 KRNL386.EXE. It shouldn't be needed otherwise.
166 .BI \--nm-cmd= nm-command
167 Specify the command to use to get the list of undefined symbols; the
170 .BI --nxcompat= yes|no
171 Specify whether the module is compatible with no-exec support. The
174 .BI \-o,\ --output= file
175 Set the name of the output file (default is standard output). If the
176 output file name end in \fB.o\fR, the text output is sent to a
177 temporary file that is then assembled to produce the specified .o
180 .BI \-r,\ --res= rsrc.res
181 Load resources from the specified binary resource file. The
182 \fIrsrc.res\fR file can be produced from a source resource file with
184 (or with a Windows resource compiler).
186 This option is only necessary for Win16 resource files, the Win32 ones
189 and will automatically be handled correctly (though the
191 option will also work for Win32 files).
194 Do not delete the various temporary files that \fBwinebuild\fR generates.
196 .BI --subsystem= subsystem[:major[.minor]]
197 Set the subsystem of the executable, which can be one of the following:
200 for a command line executable,
203 for a graphical executable,
206 for a native-mode dll,
211 The entry point of a command line executable is a normal C \fBmain\fR
212 function. A \fBwmain\fR function can be used instead if you need the
213 argument array to use Unicode strings. A graphical executable has a
214 \fBWinMain\fR entry point.
216 Optionally a major and minor subsystem version can also be specified;
217 the default subsystem version is 4.0.
219 .BI \-u,\ --undefined= symbol
220 Add \fIsymbol\fR to the list of undefined symbols when invoking the
221 linker. This makes it possible to force a specific module of a static
222 library to be included when resolving imports.
225 Display the various subcommands being invoked by
229 Display the program version and exit.
233 .SH "SPEC FILE SYNTAX"
235 A spec file should contain a list of ordinal declarations. The general
236 syntax is the following:
239 .RI [ flags ]\ exportname \ \fB(\fR\ [ args... ] \ \fB) \ [ handler ]
241 .IB ordinal\ variable
242 .RI [ flags ]\ exportname \ \fB(\fR\ [ data... ] \ \fB)
245 .RI [ flags ]\ exportname \ [ symbolname ]
248 .RI [ flags ]\ exportname \ [\ \fB( args... \fB)\fR\ ]
251 .RI [ flags ]\ exportname\ data
255 Declarations must fit on a single line, except if the end of line is
256 escaped using a backslash character. The
258 character anywhere in a line causes the rest of the line to be ignored
262 specifies the ordinal number corresponding to the entry point, or '@'
263 for automatic ordinal allocation (Win32 only).
266 is a series of optional flags, preceded by a '-' character. The
271 The entry point is not displayed in relay debugging traces (Win32
275 The entry point will be exported by ordinal instead of by name. The
276 name is still available for importing.
279 The function returns a 16-bit value (Win16 only).
282 The function returns a 64-bit value (Win32 only).
285 The function uses CPU register to pass arguments.
288 The function cannot be imported from other dlls, it can only be
289 accessed through GetProcAddress.
292 The entry point will be imported by ordinal instead of by name. The
293 name is still exported.
296 The entry point is only available on the specified CPU
297 architecture(s). The names \fBwin32\fR and \fBwin64\fR match all
298 32-bit, respectively 64-bit, CPU architectures. In 16-bit dlls,
299 specifying \fB-arch=win32\fR causes the entry point to be exported
300 from the 32-bit wrapper module.
301 .SS "Function ordinals"
305 .RI [ flags ]\ exportname \ \fB(\fR\ [ args... ] \ \fB) \ [ handler ]
308 This declaration defines a function entry point. The prototype defined by
309 .IR exportname \ \fB(\fR\ [ args... ] \ \fB)
310 specifies the name available for dynamic linking and the format of the
311 arguments. '@' can be used instead of
313 for ordinal-only exports.
320 for a normal Win32 function
323 for a normal Win16 function
326 for a Win16 or Win32 function using the C calling convention
329 for a Win16 or Win32 function using the C calling convention with a
330 variable number of arguments
333 for a Win32 function using the
335 calling convention (first parameter in %ecx register on i386)
339 should be one or several of:
343 (16-bit unsigned value)
349 (pointer-sized integer value)
352 (64-bit integer value)
355 (128-bit integer value)
358 (32-bit floating point value)
361 (64-bit floating point value)
367 (linear pointer to a null-terminated ASCII string)
370 (linear pointer to a null-terminated Unicode string)
376 (segmented pointer to a null-terminated ASCII string).
378 Note: The 16-bit and segmented pointer types are only valid for Win16
383 is the name of the actual C function that will implement that entry
384 point in 32-bit mode. The handler can also be specified as
385 .IB dllname . function
386 to define a forwarded function (one whose implementation is in another
389 is not specified, it is assumed to be identical to
392 This first example defines an entry point for the 32-bit GetFocus()
395 @ stdcall GetFocus() GetFocus
397 This second example defines an entry point for the 16-bit
398 CreateWindow() call (the ordinal 100 is just an example); it also
399 shows how long lines can be split using a backslash:
401 100 pascal CreateWindow(ptr ptr long s_word s_word s_word \\
402 s_word word word word ptr) WIN_CreateWindow
404 To declare a function using a variable number of arguments, specify
407 and declare it in the C file with a '...' parameter for a Win32
408 function, or with an extra VA_LIST16 argument for a Win16 function.
409 See the wsprintf* functions in user.exe.spec and user32.spec for an
411 .SS "Variable ordinals"
414 .IB ordinal\ variable
415 .RI [ flags ]\ exportname \ \fB(\fR\ [ data... ] \ \fB)
417 This declaration defines data storage as 32-bit words at the ordinal
420 will be the name available for dynamic
423 can be a decimal number or a hex number preceded by "0x". The
424 following example defines the variable VariableA at ordinal 2 and
427 2 variable VariableA(-1 0xff 0 0)
429 This declaration only works in Win16 spec files. In Win32 you should
433 .SS "Extern ordinals"
437 .RI [ flags ]\ exportname \ [ symbolname ]
439 This declaration defines an entry that simply maps to a C symbol
440 (variable or function). It only works in Win32 spec files.
442 will point to the symbol
444 that must be defined in the C code. Alternatively, it can be of the
446 .IB dllname . symbolname
447 to define a forwarded symbol (one whose implementation is in another
450 is not specified, it is assumed to be identical to
456 .RI [ flags ]\ exportname \ [\ \fB( args... \fB)\fR\ ]
458 This declaration defines a stub function. It makes the name and
459 ordinal available for dynamic linking, but will terminate execution
460 with an error message if the function is ever called.
461 .SS "Equate ordinals"
465 .RI [ flags ]\ exportname\ data
467 This declaration defines an ordinal as an absolute value.
469 will be the name available for dynamic linking.
471 can be a decimal number or a hex number preceded by "0x".
474 has been worked on by many people over the years. The main authors are
475 Robert J. Amstadt, Alexandre Julliard, Martin von Loewis, Ulrich
476 Weigand and Eric Youngdale. Many other Wine developers have
477 contributed, please check the file Changelog in the Wine distribution
478 for the complete details.
480 It is not yet possible to use a PE-format dll in an import
481 specification; only Wine dlls can be imported.
483 If you find a bug, please submit a bug report at
484 .UR http://bugs.winehq.org
485 .B http://bugs.winehq.org.
489 is part of the wine distribution, which is available through WineHQ,
492 development headquarters, at
493 .UR http://www.winehq.org/
494 .B http://www.winehq.org/.
projects / wine / blob