Version 10 (modified by, 14 years ago) (diff)

environment updates

Building on Windows

There is a decent amount of setup work before building of JavaScriptCore and WebCore on Windows. There are also some areas of the code which are not entirely fleshed out yet on Win32. This page serves to document those issues.

Build Environment Setup

  • Install a compiler:
  • Download and install cygwin. On the package selection screen, make sure to select the following packages! (They are not part of the default install):
     bison         (Devel)
     curl          (Net)
     flex          (Devel)
     gcc           (Devel, we only use cpp)
     gperf         (Devel))
     make          (Devel)
     patch         (Utils)
     perl          (Perl)
     perl-libwin32 (Perl)
     pkg-config    (Devel)
     subversion    (Devel)
     unzip         (Archive)
    The default text file type must be set to DOS / text during installation.
  • Check out WebKit in the usual way. Make sure that the path to the checkout directory does not contain spaces (e.g. 'Documents and Settings'), the Perl build scripts cannot handle this.
  • Install other dependencies needed by WebKit. There are two ways to do this:
  • Configure your environment variables. If you ran install-win-extras, this is already done. Otherwise, consider setting the following environment variables:
    • WebKitOutputDir to c:\WebKitBuild (this is an optional location.)
    • Path to include WebKitTools/Scripts, c:\Program Files\Resource Kit, and c:\cygwin\bin
  • Optional: if you would like an IRC client for Windows, try mIRC, X-Chat, or Trillian. If you want a non-IE browser, try Firefox or Opera.


From within Visual Studio

To build from within Visual Studio, open up WebKitTools/Spinneret/Spinneret.sln in Visual Studio. There are two configurations, Debug and Release; building one will not clobber the other. The solution will build JavaScriptCore and WebCore as dependencies, and finally the Spinneret test app.

From the command line

To build from the command line, you use the following syntax:


This will build both JavaScriptCore and WebCore in Release mode.

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.

Areas needing improvement

TODO: fill me in?

  • Describe DLL registration step