Changes between Initial Version and Version 1 of BuildingGdk


Ignore:
Timestamp:
Nov 14, 2006 2:11:47 AM (17 years ago)
Author:
alp@atoker.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildingGdk

    v1 v1  
     1[[PageOutline]]
     2
     3= Building the Gdk port =
     4
     5The Gdk port of WebKit is intended to provide a browser component primarily for users of the portable [http://www.gtk.org/ Gtk+] UI toolkit on platforms like Linux.
     6
     7== Status of the port ==
     8
     9The port is not fully-maintained, but contributors often provide changes to keep it in sync with the rest of WebKit. This means that it may not always be in a state where it builds, and even if it builds, it may not be in a working state. The goal is to change this and make it an actively maintained port.
     10
     11Developers interested in using or contributing to the Gdk port should be willing to get their hands dirty at this stage. Patches are welcomed on the bug tracker and help is readily available on the IRC channel and mailing list for developers who want to learn the ropes.
     12
     13== Dependencies ==
     14
     15The code should be easily built on any Linux distribution which has development packages for Gtk+ installed.
     16
     17== Using the Bakefile build system ==
     18
     19[http://trac.webkit.org/projects/webkit/browser/trunk/Bakefiles/Readme.txt Bakefiles/Readme.txt] describes the first step, which involves generating GNU Makefiles from a description of the sources and dependencies. It is important to use the version of Bakefile linked to in that file as versions of Bakefile with the same version number provided in Linux distributions today do not have the necessary patches to build WebKit.
     20
     21Once this is done, running "make" in WebKit/WebCore/Projects/gdk should build the library in one step, yielding libwebcore-gdk.so
     22
     23== Testing the port ==
     24
     25Running "make" in WebKit/WebKitTools/GdkLauncher will build a test browser. Due to API changes, it is possible that linking will fail, in which case the port will need to be updated to track the latest WebCore API.
     26
     27= Hacking =
     28
     29== Code layout ==
     30
     31[http://trac.webkit.org/projects/webkit/browser/trunk/WebCore/platform/gdk WebCore/platform/gdk]
     32
     33== Development roadmap ==
     34
     35 * Track recent API changes in platform/loader
     36 * Integrate the [http://bugs.webkit.org/show_bug.cgi?id=11332 SVG/Cairo support patch]
     37 * Implement more stubs
     38 * Investigate more sharing of code with the Qt port to avoid duplication of boilerplate and UI-agnostic code