1 This document should help new developers get started. Like all of Wine, it
8 The Wine source tree is loosely based on the original Windows modules.
9 Most of the source is concerned with implementing the Wine API, although
10 there are also various tools, documentation, sample Winelib code, and
11 code specific to the binary loader. Note that several of the libraries
12 listed here are "stubbed out", meaning they still need to be implemented.
17 advapi32/ - Crypto, systeminfo, security, eventlogging
18 amstream/ - MultiMedia Streams
19 avicap32/ - AVI capture window class
20 avifil32/ - COM object to play AVI files
21 cabinet/ - Cabinet file interface
22 capi2032/ - Wrapper library for CAPI4Linux access
23 cards/ - Card graphics
24 cfgmgr32/ - Config manager
25 comcat/ - Component category manager
26 comctl32/ - Common controls
27 commdlg/ - Common dialog boxes (both 16 & 32 bit)
28 crtdll/ - Old C runtime library
29 crypt32/ - Cryptography
30 ctl3d/ - 3D Effects for Common GUI Components
31 d3d8/ - Direct3D (3D graphics)
32 d3d9/ - Direct3D (3D graphics)
33 d3dim/ - Direct3D Immediate Mode
34 d3dx8/ - Direct3D (3D graphics)
35 dbghelp/ - Engine for symbol and module enumeration
36 dciman32/ - DCI Manager (graphics)
37 ddraw/ - DirectDraw (graphics)
38 devenum/ - Device enumeration (part of DirectShow)
39 dinput/ - DirectInput (device input)
40 dinput8/ - DirectInput (device input)
41 dmband/ - DirectMusic Band
42 dmcompos/ - DirectMusic Composer
43 dmime/ - DirectMusic Interactive Engine
44 dmloader/ - DirectMusic Loader
45 dmscript/ - DirectMusic Scripting
46 dmstyle/ - DirectMusic Style Engine
47 dmsynth/ - DirectMusic Software Synthesizer
48 dmusic/ - DirectMusic Core Services
49 dmusic32/ - DirectMusic Legacy Port
50 dplay/ - DirectPlay (networking)
51 dplayx/ - DirectPlay (networking)
52 dpnet/ - DirectPlay (networking)
53 dpnhpast/ - DirectPlay NAT Helper PAST
54 dsound/ - DirectSound (audio)
55 dswave/ - DirectMusic Wave
56 dxdiagn/ - DirectX Diagnostic Tool
58 glu32/ - OpenGL Utility library (graphics)
59 glut32/ - OpenGL Utility Toolkit
60 hhctrl.ocx/ - HHCTRL OCX implementation
61 iccvid/ - Radius Cinepak Video Decoder
62 icmp/ - ICMP protocol (networking)
63 ifsmgr.vxd/ - IFSMGR VxD implementation
64 imagehlp/ - PE (Portable Executable) Image Helper lib
65 imm32/ - Input Method Manager
66 iphlpapi/ - IP Helper API
67 kernel/ - The Windows kernel
68 lzexpand/ - Lempel-Ziv compression/decompression
69 mapi32/ - Mail interface
70 mmdevldr.vxd/ - MMDEVLDR VxD implementation
71 monodebg.vxd/ - MONODEBG VxD implementation
72 mpr/ - Multi-Protocol Router (networking)
73 msacm/ - Audio Compression Manager (multimedia)
74 msacm/imaadp32/ - IMA ADPCM Audio Codec
75 msacm/msadp32/ - MS ADPCM Audio Codec
76 msacm/msg711/ - MS G711 Audio Codec (includes A-Law & MU-Law)
77 msacm/winemp3/ - Mpeg Layer 3 Audio Codec
78 msdmo/ - DirectX Media Objects
79 mshtml/ - MS HTML component
80 msi/ - Microsoft Installer
81 msimg32/ - Gradient and transparency (graphics)
82 msisys/ - System information
83 msnet32/ - Network interface
84 msvcrt/ - C runtime library
85 msvcrt20/ - C runtime library version 2.0
86 msvcrt40/ - C runtime library version 4.0
87 msvcrtd/ - C runtime library debugging
88 msvidc32/ - Microsoft Video-1 Decoder
89 msvideo/ - 16 bit video manager
90 msvideo/msrle32/ - Video codecs
91 mswsock/ - Misc networking
92 netapi32/ - Network interface
93 newdev/ - New Hardware Device Library
94 ntdll/ - NT implementation of kernel calls
95 odbc32/ - Open DataBase Connectivity driver manager
96 ole32/ - 32 bit OLE 2.0 libraries
97 oleacc/ - OLE accessibility support
98 oleaut32/ - 32 bit OLE 2.0 automation
99 olecli/ - 16 bit OLE client
100 oledlg/ - OLE 2.0 user interface support
101 olepro32/ - 32 bit OLE 2.0 automation
102 olesvr/ - 16 bit OLE server
103 opengl32/ - OpenGL implementation (graphics)
104 psapi/ - Process Status interface
105 qcap/ - DirectShow runtime
106 quartz/ - DirectShow runtime
107 rasapi32/ - Remote Access Server interface
108 richedit/ - Rich text editing control
109 rpcrt4/ - Remote Procedure Call runtime
110 rsabase/ - RSA encryption
111 secur32/ - Contains Windows Security functions
112 serialui/ - Serial port property pages
113 setupapi/ - Setup interface
114 setupx/ - Contains functions used by the Windows Setup
115 shdocvw/ - Shell document object and control
116 shell32/ - COM object implementing shell views
117 shfolder/ - Shell folder service
118 shlwapi/ - Shell Light-Weight interface
119 snmpapi/ - SNMP protocol interface (networking)
120 sti/ - Still Image service
121 tapi32/ - Telephone interface
122 ttydrv/ - TTY display driver (Wine specific)
123 twain/ - TWAIN Imaging device communications
124 unicows/ - Unicows replacement (Unicode layer for Win9x)
125 url/ - Internet shortcut shell extension
126 urlmon/ - URL Moniker allows binding to a URL (like KIO/gnome-vfs)
127 user/ - Window management, standard controls, etc.
128 uxtheme/ - Theme library
129 vdhcp.vxd/ - VDHCP VxD implementation
130 version/ - File installation library
131 vmm.vxd/ - VMM VxD implementation
132 vnbt.vxd/ - VNBT VxD implementation
133 vnetbios.vxd/ - VNETBIOS VxD implementation
134 vtdapi.vxd/ - VTDAPI VxD implementation
135 vwin32.vxd/ - VWIN32 VxD implementation
136 win32s/ - 32-bit function access for 16-bit systems
137 winaspi/ - 16 bit Advanced SCSI Peripheral Interface
138 wined3d/ - Wine internal Direct3D helper
139 winedos/ - DOS features and BIOS calls (interrupts) (wine specific)
140 wineps/ - Postscript driver (Wine specific)
141 wininet/ - Internet extensions
142 winmm/ - Multimedia (16 & 32 bit)
143 winmm/joystick/ - Joystick driver
144 winmm/mcianim/ - MCI animation driver
145 winmm/mciavi/ - MCI video driver
146 winmm/mcicda/ - MCI audio CD driver
147 winmm/mciseq/ - MCI MIDI driver
148 winmm/mciwave/ - MCI wave driver
149 winmm/midimap/ - MIDI mapper
150 winmm/wavemap/ - Audio mapper
151 winmm/winealsa/ - ALSA audio driver
152 winmm/winearts/ - aRts audio driver
153 winmm/wineaudioio/ - audioio audio driver
154 winmm/winejack/ - JACK audio server driver
155 winmm/winenas/ - NAS audio driver
156 winmm/wineoss/ - OSS audio driver
157 winnls/ - National Language Support
158 winsock/ - Sockets 2.0 (networking)
159 winspool/ - Printing & Print Spooler
160 wintab32/ - Tablet device interface
161 wintrust/ - Trust verification interface
162 wow32/ - WOW subsystem
163 wsock32/ - Sockets 1.1 (networking)
164 x11drv/ - X11 display driver (Wine specific)
166 Winelib programs (under programs/):
167 -----------------------------------
169 avitools/ - AVI information viewer and player
170 clock/ - Graphical clock
171 cmdlgtst/ - Common dialog tests
172 control/ - Control panel
173 expand/ - Decompress Lempel-Ziv compressed archive
174 notepad/ - Notepad replacement
175 progman/ - Program manager
176 regedit/ - Registry editor
177 regsvr32/ - Register COM server
178 rpcss/ - RPC services
179 rundll32/ - Execute DLL functions directly
180 start/ - Replacement for start.exe
181 taskmgr/ - Manage running Windows/Winelib applications
182 uninstaller/ - Remove installed programs
183 view/ - Metafile viewer
184 wcmd/ - Command line interface
185 wineboot/ - Wine bootstrap process
186 winecfg/ - Wine configuration utility
187 wineconsole/ - Console
189 winefile/ - File manager
190 winemenubuilder/ - Helper program for building Unix menu entries
191 winemine/ - Mine game
192 winepath/ - Translate between Wine and Unix paths
193 winetest/ - Wine testing shell
194 winevdm/ - Wine virtual DOS machine
195 winhelp/ - Help viewer
196 winver/ - Windows Version Program
199 Support programs, libraries, etc:
200 ---------------------------------
202 dlls/dxerr8/ - DirectX 8 error import lib
203 dlls/dxerr9/ - DirectX 9 error import lib
204 dlls/dxguid/ - DirectX UUID import lib
205 dlls/uuid/ - Windows-compatible UUID import lib
206 documentation/ - some documentation
207 documentation/samples/ - sample configuration files
208 include/ - Windows standard includes
209 include/msvcrt/ - MSVC compatible libc headers
210 include/wine/ - Wine specific headers
211 libs/ - the Wine libraries
212 libs/port/ - portability library
213 libs/unicode/ - Unicode support shared
214 libs/wine/ - Wine bootstrap library
215 libs/wpp/ - C preprocessor
216 loader/ - the main Wine loader
217 server/ - the Wine server
218 tools/ - various tools used to build/check Wine
219 tools/widl/ - the IDL compiler
220 tools/winapi{,_check}/ - A Win32 API checker
221 tools/winebuild/ - Wine build tool
222 tools/winedump/ - a .DLL dump utility
223 tools/winegcc/ - a MinGW command line compatible gcc wrapper
224 tools/wmc/ - the message compiler
225 tools/wpp/ - the C pre-processor library
226 tools/wrc/ - the resource compiler
232 Note: these directories will ultimately get moved into their
235 misc/ - KERNEL registry
237 objects/ - GDI logical objects
239 controls/ - USER built-in widgets
240 windows/ - USER window management
244 IMPLEMENTING NEW API CALLS
245 ==========================
247 This is the simple version, and covers only Win32. Win16 is slightly
248 uglier, because of the Pascal heritage and the segmented memory model.
250 All of the Win32 APIs known to Wine are listed in the .spec file of
251 their corresponding dll. An unimplemented call will look like (from
253 269 stub PolyBezierTo
254 To implement this call, you need to do the following four things.
256 1. Find the appropriate parameters for the call, and add a prototype to
257 the correct header file. In this case, that means [include/wingdi.h],
258 and it might look like
259 BOOL WINAPI PolyBezierTo(HDC, LPCVOID, DWORD);
260 If the function has both an ASCII and a Unicode version, you need to
261 define both and add a #define WINELIB_NAME_AW declaration. See below
262 for discussion of function naming conventions.
264 2. Modify the .spec file to tell Wine that the function has an
265 implementation, what the parameters look like and what Wine function
266 to use for the implementation. In Win32, things are simple--everything
267 is 32-bits. However, the relay code handles pointers and pointers to
268 strings slightly differently, so you should use 'str' and 'wstr' for
269 strings, 'ptr' for other pointer types, and 'long' for everything else.
270 269 stdcall PolyBezierTo(long ptr long) PolyBezierTo
271 The 'PolyBezierTo' at the end of the line is which Wine function to use
272 for the implementation.
274 3. Implement the function as a stub. Once you add the function to the .spec
275 file, you must add the function to the Wine source before it will link.
276 Add a function called 'PolyBezierTo' somewhere. Good things to put
278 o a correct prototype, including the WINAPI
279 o header comments, including full documentation for the function and
280 arguments (see documentation/README.documentation)
281 o A FIXME message and an appropriate return value are good things to
284 /************************************************************
285 * PolyBezierTo (GDI32.269)
287 * Draw many Bezier curves.
290 * hdc [I] Device context to draw to
291 * p [I] Array of POINT structs
292 * count [I] Number of points in p
296 * Failure: FALSE. Use GetLastError() to find the error cause.
301 BOOL WINAPI PolyBezierTo(HDC hdc, LPCVOID p, DWORD count)
303 /* tell the user they've got a substandard implementation */
304 FIXME(gdi, ":(%x,%p,%d): stub\n", hdc, p, count);
306 /* some programs may be able to compensate,
307 * if they know what happened
309 SetLastError(ERROR_CALL_NOT_IMPLEMENTED);
310 return FALSE; /* error value */
313 4. Implement and test the rest of the function.
316 IMPLEMENTING A NEW DLL
317 ======================
322 Apart from writing the set of needed .c files, you also need to do the
325 1. Create a directory <MyDll> where to store the implementation of
326 the DLL. This directory has to be put under the dlls/ directory.
327 If the DLL exists under Windows as both 16 and 32 bit DLL, you
328 should have a single directory with both implementations.
330 2. Create the Makefile.in in the ./dlls/<MyDll>/ directory. You can
331 copy an existing Makefile.in from another ./dlls/ subdirectory.
332 You need at least to change the MODULE and C_SRCS macros.
334 3. Add the directory in ./configure.ac (in AC_OUTPUT macro at the end
335 of the file to trigger the Makefile generation)
337 4. Run ./make_dlls in the dlls directory to update Makefile.in in
340 5. You can now regenerate ./configure file (with 'make configure')
341 and the various Makefiles (with 'configure; make depend') (run
342 from the top of Wine's tree).
343 You should now have a Makefile file in ./dlls/<MyDll>/
345 6. Create the .spec file for the DLL exported functions in your
346 directory. Refer to 'Implementation of new API calls' earlier in
347 this document for more information on this part.
349 7. You can now start adding .c files. For the .h files, if they are
350 standard Windows one, put them in include/. If they are linked to
351 *your* implementation of the dll, put them in your newly created
357 If you need to create a new debug channel, just add the
358 WINE_DEFAULT_DEBUG_CHANNEL to your .c file(s), and use them.
359 All the housekeeping will happen automatically.
364 If you also need to add resources to your DLL, then create the .rc
365 file. Add to your ./dlls/<MyDll>/Makefile.in, in the RC_SRCS macro,
366 the list of .rc files to add to the DLL. See dlls/comctl32/ for an
372 If you're building a 16 & 32 bit DLLs pair, then from the 32 bit code
373 you might need to call 16 bit routine. The way to do it to add in the
374 code, fragments like:
375 /* ### Start build ### */
376 extern WORD CALLBACK <PREFIX>_CallTo16_word_wwlll(FARPROC16,WORD,WORD,LONG,LONG,LONG);
377 /* ### stop build ### */
378 Where <PREFIX>_ is an internal prefix for your module. The first
379 parameter is always of type FARPROC16. Then, you can get the regular
380 list of parameters. The _word_wwlll indicates the type of return (long
381 or word) and the size of the parameters (here l=>long, w=>word; which
382 maps to WORD,WORD,LONG,LONG,LONG.
383 You can put several functions between the Start/Stop build pair.
385 You can also read the winebuild manpage for more details on this.
387 Then, add to ./dlls/<MyDll>/Makefile.in a line like:
389 EXTRA_OBJS = $(MODULE).glue.o
391 See dlls/winmm/ for an example of this.
396 NE (Win16) executables consist of multiple segments. The Wine loader
397 loads each segment into a unique location in the Wine processes memory
398 and assigns a selector to that segment. Because of this, it's not
399 possible to exchange addresses freely between 16-bit and 32-bit code.
400 Addresses used by 16-bit code are segmented addresses (16:16), formed
401 by a 16-bit selector and a 16-bit offset. Those used by the Wine code
402 are regular 32-bit linear addresses.
404 There are four ways to obtain a segmented pointer:
405 - Using the MapLS function (recommended).
406 - Allocate a block of memory from the global heap and use
407 WIN16_GlobalLock to get its segmented address.
408 - Declare the argument as 'segptr' instead of 'ptr' in the spec file
409 for a given API function.
411 Once you have a segmented pointer, it must be converted to a linear
412 pointer before you can use it from 32-bit code. This can be done with
413 the MapSL function. The linear pointer can then be used freely with
414 standard Unix functions like memcpy() etc. without worrying about 64k
415 boundaries. Note: there's no easy way to convert back from a linear
416 to a segmented address.
418 In most cases, you don't need to worry about segmented address, as the
419 conversion is made automatically by the callback code and the API
420 functions only see linear addresses. However, in some cases it is
421 necessary to manipulate segmented addresses; the most frequent cases
423 - API functions that return a pointer
424 - lParam of Windows messages that point to a structure
425 - Pointers contained inside structures accessed by 16-bit code.
427 It is usually a good practice to used the type 'SEGPTR' for segmented
428 pointers, instead of something like 'LPSTR' or 'char *'. As SEGPTR is
429 defined as a DWORD, you'll get a compilation warning if you mistakenly
430 use it as a regular 32-bit pointer.
436 Under Windows, data structures are tightly packed, i.e. there is no
437 padding between structure members. On the other hand, by default gcc
438 aligns structure members (e.g. WORDs are on a WORD boundary, etc.).
439 This means that a structure like
441 struct { BYTE x; WORD y; };
443 will take 3 bytes under Windows, but 4 with gcc, because gcc will add a
444 dummy byte between x and y. To have the correct layout for structures
445 used by Windows code, you need to embed the struct within two special
446 #include's which will take care of the packing for you:
448 #include "pshpack1.h"
449 struct { BYTE x; WORD y; };
450 #include "poppack1.h"
452 For alignment on a 2-byte boundary, there is a "pshpack2.h", etc.
455 NAMING CONVENTIONS FOR API FUNCTIONS AND TYPES
456 ==============================================
458 In order to support both Win16 and Win32 APIs within the same source
459 code, the following convention must be used in naming all API
460 functions and types. If the Windows API uses the name 'xxx', the Wine
463 - 'xxx16' for the Win16 version,
464 - 'xxx' for the Win32 version when no strings are involved,
465 - 'xxxA' for the Win32 version with ASCII strings,
466 - 'xxxW' for the Win32 version with Unicode strings.
468 If the function has both ASCII and Unicode version, you should then
469 use the macros WINELIB_NAME_AW(xxx) or DECL_WINELIB_TYPE_AW(xxx)
470 (defined in include/windef.h) to define the correct 'xxx' function
471 or type for Winelib. When compiling Wine itself, 'xxx' is _not_
472 defined, meaning that code inside of Wine must always specify
473 explicitly the ASCII or Unicode version.
475 If 'xxx' is the same in Win16 and Win32, you can simply use the same
476 name as Windows, i.e. just 'xxx'. If 'xxx' is Win16 only, you could
477 use the name as is, but it's preferable to use 'xxx16' to make it
478 clear it is a Win16 function.
482 typedef struct { /* Win32 ASCII data structure */ } WNDCLASSA;
483 typedef struct { /* Win32 Unicode data structure */ } WNDCLASSW;
484 typedef struct { /* Win16 data structure */ } WNDCLASS16;
485 DECL_WINELIB_TYPE_AW(WNDCLASS);
487 ATOM RegisterClass16( WNDCLASS16 * );
488 ATOM RegisterClassA( WNDCLASSA * );
489 ATOM RegisterClassW( WNDCLASSW * );
490 #define RegisterClass WINELIB_NAME_AW(RegisterClass)
492 The Winelib user can then say:
494 WNDCLASS wc = { ... };
495 RegisterClass( &wc );
497 and this will use the correct declaration depending on the definition
498 of the UNICODE symbol.
504 To display a message only during debugging, you normally write something
512 depending on the seriousness of the problem. (documentation/debugging.sgml
513 explains when it is appropriate to use each of them). You need to declare
514 the debug channel name at the top of the file (after the includes) using
515 the WINE_DEFAULT_DEBUG_CHANNEL macro, like so:
517 WINE_DEFAULT_DEBUG_CHANNEL(win);
519 If your debugging code is more complex than just printf, you can use
522 TRACE_ON(xxx), WARN_ON(xxx), ERR_ON(xxx) and FIXME_ON(xxx)
524 to test if the given channel is enabled. Thus, you can write:
526 if (TRACE_ON(win)) DumpSomeStructure(&str);
528 Don't worry about the inefficiency of the test. If it is permanently
529 disabled (that is TRACE_ON(win) is 0 at compile time), the compiler will
530 eliminate the dead code.
532 For more info about debugging messages, read:
534 http://www.winehq.org/site/docs/wine-devel/debugging
540 1. There is a FREE online version of the MSDN library (including
541 documentation for the Win32 API) on http://msdn.microsoft.com/
542 or http://www.msdn.com/
544 2. Windows apilist: http://www.mentalis.org/apilist/apilist.php
546 3. http://www.sonic.net/~undoc/bookstore.html
548 4. In 1993 Dr. Dobbs Journal published a column called "Undocumented Corner".
550 5. www.geocities.com/SiliconValley/4942/
projects / wine / blob