Changes between Initial Version and Version 1 of BuildingCairoOnWindows


Ignore:
Timestamp:
Feb 10, 2008 4:37:28 PM (16 years ago)
Author:
bfulgham@macports.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildingCairoOnWindows

    v1 v1  
     1[[PageOutline]]
     2
     3= Building on Windows =
     4As with [wiki:"BuildingOnWindows" 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.
     5
     6Note 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.
     7
     8== Required Libraries ==
     9At the moment, you will need to manually obtain the following librareis:
     10 * [http://gnuwin32.sourceforge.net/packages/giflib.htm GIFLIB] - GIF libraris (both the -bin and -lib packges).
     11 * [http://gnuwin32.sourceforge.net/packages/jpeg.htm libJPEG] - JPEG libraries (both the -bin and -lib packages).
     12 * [http://gnuwin32.sourceforge.net/packages/libpng.htm libPNG] - PNG libraries (both the -bin and -lib packages).
     13 * [http://www.cairographics.org Cairo]
     14
     15== Building from within Visual Studio ==
     16WebKit can be built from within Visual Studio by setting two environment variables:
     17 * {{{WEBKITOUTPUTDIR}}} - An absolute Windows-style path pointing to the directory where you want the build products to go.
     18 * {{{WEBKITLIBRARIESDIR}}} - An absolute Windows-style path pointing to the WebKitLibraries/win folder in your WebKit checkout.
     19
     20== Common Build Errors ==
     21=== Error spawning cmd.exe ===
     22Sometimes, 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).
     23
     24=== Bad line endings ===
     25When 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.
     26
     27=== Visual C++ Express Edition ===
     28{{{
     291>c:\cygwin\home\admin\webkit\javascriptcore\wtf\assertions.cpp(45) : fatal error C1083: Cannot open include file: 'windows.h': No such file or directory
     30}}}
     31
     32If you see errors like this you probably need to install the [http://msdn.microsoft.com/vstudio/express/visualc/usingpsdk/ platform SDK].
     33
     34== Running the tests ==
     35After 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.)