CS130 Winter 2008 - Wine / GDI+

Windows Programming

GDI+

GDI+ is a new version of GDI with more advanced graphics features. GDI is a Windows susbsystem that draws shapes, render fonts, etc.

GDI+ Programming

TODO: General description of GDI+ Programming. Links, etc.

List of GDI+ Functions

The table below lists the GDI+ functions known to be in use, along with the number of applications that use it.

The table is sortable if you click on the table headers.

Compiling on Win32

Compiling Wine Tests on Windows

We need to make sure the conformance tests we write work on Windows to begin with. This means we need to compile and run the tests on Windows.

With GDI+, the Windows SDK header files conflict with the Wine gdiplus header files. To get around that, do the following:

Copy wine-version/include/gdiplus*.h to wine-version/dlls/gdiplus/tests/wine/.

You also need to copy wine-version/include/wine/test.h to wine-version/dlls/gdiplus/tests/wine/test.h. Then, from wine-version/dlls/gdiplus/tests, run:

cl -DSTANDALONE -D_X86_ foo.c gdiplus.lib -I .\wine

This will generate the test program foo.exe.

Working with Wine

Useful Links

Documentation

Browsing the code

Mailing lists

Conformance Tests

Wine Test Macros

Wine has a couple useful macros for testing.

The first one is ok().

ok(test, output_msg, args...);

test can be anything statement, and if it evaluates to true, then the test passes. Otherwise, the test fails and Wine prints an error message.

output_msg, args... - output_msg is a string in the same format used by printf() and args... are the variable arguments for values in the format string.

Example: result = MyFunction(arg1, arg2, arg3); ok(result == 5, "Expected 5, got %d\n", r);

Sometimes a test case will work on Windows, but it is known not to work with Wine. For such a case, put it inside a todo_wine() statement. This has several effects: (1) the failure is listed as a todo instead, (2) when the problem gets fixed eventually, the todo will become a failure to alert you, (3) this separates known failures from new failures that can occur through regression.

Compiling Wine

Compiling the entire Wine tree can be a time consuming process (8-20 minutes on a modern machine. Fortunately, most of the time we will just be making changes in the dlls/gdiplus/ directory, so it's not so bad. If you are on a multi-core/processor machine, remember to use make's -j option to speed up the process.

Compiling Windows Program with Wine

To compile Windows program with Wine, use winegcc/wineg++. It takes the same arguments as gcc, so to compile and link a program with gdiplus, run: winegcc -o foo foo.c -lgdiplus.

GIT

Submitting Patches

Bugzilla

Sample bug

Outstanding Bugs