Changes between Version 44 and Version 45 of WebKitGTK/StartHacking


Ignore:
Timestamp:
Oct 1, 2014 7:50:06 AM (7 years ago)
Author:
Andres Gomez
Comment:

Updating instructions due to migration to CMake and removal of WebKit1 code

Legend:

Unmodified
Added
Removed
Modified
  • WebKitGTK/StartHacking

    v44 v45  
    100100   * In any case, don't worry too much since a ''Release'' and a ''Debug'' build can co-exist as WebKit store the resulting objects in different directories.
    101101 * Also, there is the possibility to ''tweak'' a ''Release'' build to keep [wiki:WebKitGTK/Debugging#DebuggingWebKitGTK certain debugging helpers] and yet not being a full ''Debug'' build. For example, you may want to disable the compilation of unneeded pieces for if you are not working on them. For example, you can pass:
    102    * Disable GTK doc: --disable-gtk-doc
    103    * Disable WebKit1: --no-webkit1
    104 {{{
    105 #!sh
    106 $ Tools/Scripts/build-webkit --gtk --disable-gtk-doc --no-webkit1
     102{{{
     103#!sh
     104$ Tools/Scripts/build-webkit --gtk
    107105}}}
    108106   * You may also want to turn some debugging flags in a ''Release'' build. For example, you can turn on the logging support setting the C macro ''LOG_DISABLED=0''.
     
    112110$ ./Tools/Scripts/build-webkit --gtk
    113111}}}
    114  * You may also want to pass extra parameters to the ''make'' command. This can be done with the ''--makeargs'' argument:
    115 {{{
    116 #!sh
    117 $ ./Tools/Scripts/build-webkit --gtk --makeargs="-j2"
     112 * You may also want to pass extra parameters to the ''cmake'' command. This can be done with the ''--cmakeargs'' argument:
     113{{{
     114#!sh
     115$ ./Tools/Scripts/build-webkit --release --gtk --cmakeargs="-GNinja -j8"
    118116}}}
    119117 * You should check all the possible flags to pass to the building script:
     
    238236WebKit provides a really complete set of tets to check the code and your changes. You can get more information about them in WebKitGtkLayoutTests.
    239237
    240 In addition, you may want to check your changes in an actual application. WebKit provides a dummy browser in which to do so. GTK+ port actually has GtkLauncher, featuring WebKit1 and MiniBrowser, featuring WebKit2.
    241 
    242  * To run GtkLauncher:
     238In addition, you may want to check your changes in an actual application. WebKit provides a dummy browser in which to do so. GTK+ port actually has MiniBrowser.
     239
     240 * To run MiniBrowser:
    243241{{{
    244242#!sh
    245243$ Tools/Scripts/run-launcher --gtk
    246244}}}
    247  * To run MiniBrowser (WebKit2):
    248 {{{
    249 #!sh
    250 $ Tools/Scripts/run-launcher --gtk -2
    251 }}}
    252245
    253246Of course, this can be done also manually from the ''jhbuild'' shell:
     
    255248#!sh
    256249$ Tools/jhbuild/jhbuild-wrapper --gtk shell
    257 $ WebKitBuild/Release/Programs/GtkLauncher &
    258250$ WebKitBuild/Release/Programs/MiniBrowser &
    259251}}}