Version 15 (modified by, 13 years ago) (diff)


Building on Windows

As with Apple's Windows Port, you must first follow the instructions on to install the necessary developer tools, support libraries, and check out the WebKit code.

Note that it is safest to build WebKit in your Cygwin home directory (c:\cygwin\home\username\WebKit). At the moment, there seems to be an implicit assumption in the build scripts that paths will be relative to the home directory.

In the ~/WebKit/Tools/Scripts folder, use

./build-webkit --wincairo

to start the build.

Required Libraries

Just like the CoreGraphics Windows and Mac build, you must have the QuickTime SDK installed. In addition, you will need to manually obtain the following libraries:

  • libJPEG - JPEG libraries. Since all existing win32 versions of this library seem to be missing important patches, I would recommend downloading the source source tarball, then apply the debian patches. You can then build it from the DOS shell using the included I generally build the static library and link it directly to WebKit.
  • libPNG - PNG libraries (both the -bin and -lib packages).
  • Cairo - Cairo libraries (both the -bin and -dev packages).
  • cURL - Curl software. I generally build this from source.

For convenience, I have bundled up my copies of these items for easy download.

Once you have them, unpack them someplace (such as C:\WebKit\requirements) and add the underlying include and lib directories to the Visual Studio Directory list.

Building from within Visual Studio

WebKit can be built from within Visual Studio by setting two environment variables:

  • WEBKITOUTPUTDIR - An absolute Windows-style path pointing to the directory where you want the build products to go.
  • WEBKITLIBRARIESDIR - An absolute Windows-style path pointing to the WebKitLibraries/win folder in your WebKit checkout.

Common Build Errors

Error spawning cmd.exe

Sometimes, Visual Studio complains that it 'cannot spawn cmd.exe'. Should this happen, check if both your Cygwin\bin folder and c:\windows\sytem32 are both in the Visual Studio list of executable files (Tools -> Options -> VC++ Directories).

Bad line endings

When you see errors in WebCore/css/makeprops or WebCore/css/maketokenizer, open those files in a suitable editor (SciTE works) and convert the line endings to LF only (Unix-style). Then restart the build.

Missing Autogenerated Files

If you have the Visual Studio IDE open while you are performing an update-webkit, you can sometimes run into a strange problem where Visual Studio is unable to locate the autogenerated files. These files are usually things like HTMLNames.cpp, which are generated by Perl as part of the WebCoreGenerated target.

The best way to resolve this is to exit from the IDE, then relaunch. This usually fixes the problem, though you may wish to clean and rebuild the JavaScriptCoreGenerated and WebCoreGenerated projects.

Visual C++ Express Edition

1>c:\cygwin\home\admin\webkit\javascriptcore\wtf\assertions.cpp(45) : fatal error C1083: Cannot open include file: 'windows.h': No such file or directory

If you see errors like this you probably need to install the platform SDK.

Running the tests

After successfully building WebKit, in order to run the tests you need to:

  1. copy the DLLs from C:\Program Files\Safari\ into your WebKitBuild\bin folder, otherwise jsc won't run properly. When you are doing this, be careful not to overwrite the WebKit.dll file in WebKitBuild\bin with the one in C:\Program Files\Safari. (If you use the DOS copy command, it will ask you before overwriting.)
  2. Make sure the Cairo, JPEG, and PNG libraries are either in this directory, or in your PATH.

Note: Safari will most likely not work, as various methods needed for Safari may not be implemented. I am only aware of WinLauncher working with Cairo-based WebKit at this time.