Changes between Version 19 and Version 20 of BuildingCairoOnWindows


Ignore:
Timestamp:
Jun 13, 2013, 8:57:33 AM (11 years ago)
Author:
bfulgham@webkit.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BuildingCairoOnWindows

    v19 v20  
    1818== Building from within Visual Studio ==
    1919WebKit can be built from within Visual Studio by setting two environment variables:
    20  * {{{WEBKITOUTPUTDIR}}} - An absolute Windows-style path pointing to the directory where you want the build products to go.
    21  * {{{WEBKITLIBRARIESDIR}}} - An absolute Windows-style path pointing to the WebKitLibraries/win folder in your WebKit checkout.
     20 * {{{WEBKIT_OUTPUTDIR}}} - An absolute Windows-style path pointing to the directory where you want the build products to go.
     21 * {{{WEBKIT_LIBRARIES}}} - An absolute Windows-style path pointing to the WebKitLibraries/win folder in your WebKit checkout.
    2222
    2323== Common Build Errors ==
    2424=== Error spawning cmd.exe ===
    25 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).
     25Sometimes, 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).
    2626
    2727=== Bad line endings ===
    28 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.
     28When 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). You can also use the `dos2unix` command from the Cygwin shell. Then restart the build.
    2929
    3030=== Missing Autogenerated Files ===
    31 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.
     31If 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.
    3232
    3333The 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.
    … …  
    3737{{{
    3838webkitpy.common.system.autoinstall: INFO     Auto-installing package: eliza.py
    39 webkitpy.common.system.autoinstall: INFO         From: "http://www.adambarth.com
    40 /webkit/eliza"
    41 webkitpy.common.system.autoinstall: INFO           To: "/cygdrive/e/Projects/Web
    42 Kit/Tools/Scripts/webkitpy/thirdparty/autoinstalled/eliza.py"
     39webkitpy.common.system.autoinstall: INFO         From: "http://www.adambarth.com/webkit/eliza"
     40webkitpy.common.system.autoinstall: INFO           To: "/cygdrive/e/Projects/WebKit/Tools/Scripts/webkitpy/thirdparty/autoinstalled/eliza.py"
    4341Traceback (most recent call last):
    44   File "/cygdrive/e/Projects/WebKit/Tools/Scripts/test-webkitpy", line 266, in <
    45 module>
     42  File "/cygdrive/e/Projects/WebKit/Tools/Scripts/test-webkitpy", line 266, in <module>
    4643    Tester().run_tests(sys.argv, external_package_paths)
    4744  File "/cygdrive/e/Projects/WebKit/Tools/Scripts/webkitpy/test/main.py", line 1
    … …  
    5956== Running the tests ==
    6057After successfully building WebKit, in order to run the tests you need to:
    61   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.)
     58  1. copy the DLLs from `%WEBKIT_LIBRARIES%\bin32\` into your build output folder, otherwise {{{jsc}}} won't run properly.
    6259  1. Make sure the Cairo, JPEG, and PNG libraries are either in this directory, or in your PATH.
    63 
    64 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.