Changes between Version 13 and Version 14 of BuildingOnWindows


Ignore:
Timestamp:
Dec 28, 2007 5:36:16 PM (14 years ago)
Author:
webkit@mattlilek.com
Comment:

Add info on building in VS

Legend:

Unmodified
Added
Removed
Modified
  • BuildingOnWindows

    v13 v14  
    22
    33= Building on Windows =
    4 
    54Follow the instructions on http://webkit.org/building/tools.html to install the necessary developer tools, support libraries, and check out the WebKit code.
    65
    76Note 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.
    87
     8== Building from within Visual Studio ==
     9WebKit can be built from within Visual Studio by setting two environment variables:
     10 * {{{WEBKITOUTPUTDIR}}} - An absolute Windows-style path pointing to the directory where you want the build products to go.
     11 * {{{WEBKITLIBRARIESDIR}}} - An absolute Windows-style path pointing to the WebKitLibraries/win folder in your WebKit checkout.
     12
    913== Common Build Errors ==
    10 
    1114=== Error spawning cmd.exe ===
    1215Sometimes, 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).
     
    2326
    2427== Running the tests ==
    25 
    2628After 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.)
    27 
    28 == Areas needing improvement ==
    29 
    30 __TODO__: fill me in?
    31 
    32  * Describe DLL registration step