Version 5 (modified by 17 years ago) ( diff ) | ,
---|
Building on Windows
As with Apple's Windows Port, you must first follow the instructions on http://webkit.org/building/tools.html 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. At the moment, there seems to be an implicit assumption in the build scripts that paths will be relative to the home directory.
Required Libraries
At the moment, you will need to manually obtain the following libraries:
- GIFLIB - GIF libraries (both the -bin and -lib packges).
- libJPEG - JPEG libraries (both the -bin and -lib packages). Note that this library seems buggy. I suggest building from sources as there are several ways JPEGs can cause this library to crash.
- libPNG - PNG libraries (both the -bin and -lib packages).
- Cairo - Cairo libraries (both the -bin and -dev packages).
Once you have them, unpack them someplace (such as C:\graphics_formats) 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.
Configuring the build
You must update the WebCore/config.h file to indicate that you wish to build with Cairo.
#if 0 #if PLATFORM(WIN) // Safari-style build #define WTF_USE_JAVASCRIPTCORE_BINDINGS 1 #define WTF_USE_NPOBJECT 1 #define WTF_PLATFORM_CG 1 #undef WTF_PLATFORM_CAIRO #define WTF_USE_CFNETWORK 1 #undef WTF_USE_WININET #define WTF_PLATFORM_CF 1 #define WTF_USE_PTHREADS 0 #endif #else #if PLATFORM(WIN) #if 1 // Cairo-style build (stock everything else) #define WTF_USE_JAVASCRIPTCORE_BINDINGS 1 #define WTF_USE_NPOBJECT 1 #undef WTF_USE_CURL #define WTF_PLATFORM_CAIRO 1 #define WTF_USE_CFNETWORK 1 #undef WTF_USE_WININET #define WTF_PLATFORM_CF 1 #define WTF_USE_PTHREADS 0 #else // Completely redistributable #define WTF_USE_JAVASCRIPTCORE_BINDINGS 1 #define WTF_USE_NPOBJECT 1 #define WTF_USE_CURL 1 #define WTF_PLATFORM_CAIRO 1 #undef WTF_USE_CFNETWORK #undef WTF_USE_WININET #define WTF_PLATFORM_CF 1 #define WTF_USE_PTHREADS 0 #endif
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.
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 copy the DLLs from C:\Program Files\Safari\ into your WebKitBuild\bin folder, otherwise testkjs 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.)