Changes between Version 6 and Version 7 of WebKitGTK/StartHacking

Timestamp:

Jun 19, 2013 9:09:51 AM (10 years ago)

Author:

Andres Gomez

Comment:

Added continuous integration section

WebKitGTK/StartHacking

@@ -68 +68 @@
 
 There are a couple of things still to be considered:
- * ''Release'' or ''Debug''? The default compilation will do a ''Release'' build. You may think that it may be worthy to actually do a ''Debug'' build since you are planning to start hacking and make use of ''gdb''. However, a ''Debug'' build will take longer, more hard drive space and more RAM. In addition, running a debug build in ''gdb'' may be a pain. Because of this, most of the WebKit hackers choose to just use a ''Release'' build and make an extensive usage of ''printf'' as debugging tool. Also, there is the possibility to ''tweak'' a ''Release'' build to keep certain debugging helpers and yet not being a full ''Debug'' build.
+ * ''Release'' or ''Debug''? The default compilation will do a ''Release'' build. You may think that it may be worthy to actually do a ''Debug'' build since you are planning to start hacking and make use of ''gdb''. However, a ''Debug'' build will take longer, more hard drive space and more RAM. In addition, running a debug build in ''gdb'' may be a pain. Because of this, most of the WebKit hackers choose to just use a ''Release'' build and make an extensive usage of ''printf'' as debugging tool. 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.
  - 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.
  * You may want to disable the compilation of unneeded pieces for if you are not working on them. For example, you can pass:
@@ -139 +139 @@
 
 
-=== Testing ===
+== Testing ==
 
 WebKit provides a really complete set of tets to check the code and your changes. You can get more information about them in WebKitGtkLayoutTests.
@@ -150 +150 @@
 $ Tools/Scripts/run-launcher --gtk
 }}}
- * To run @MiniBrowser@ (WebKit2):
+ * To run MiniBrowser (WebKit2):
 {{{
 #!sh
@@ -163 +163 @@
 $ WebKitBuild/Release/Programs/MiniBrowser &
 }}}
+
+
+== Debugging ==
+
+Here you have some [wiki:WebKitGTK/Debugging debugging tips] and also some other tips for [wiki:WebKitGTK/TrackingMemoryErrors tracking memory errors].
+
+
+== Continuous integration ==
+
+WebKit continuous integration happens in http://build.webkit.org/. There are a number of ''gardening'' guidelines to help [wiki:WebKitGTK/KeepingTheTreeGreen keeping our build bots green].
+
+
+
+