Changes between Version 15 and Version 16 of HackingGtk

Timestamp:

May 8, 2009 11:54:30 AM (15 years ago)

Author:

kov@webkit.org

Comment:

--

HackingGtk

@@ -114 +114 @@
 This helps keep all the ports buildable. There is also compile output provided which is helpful for understanding the build environments and compiler flags used by other ports and tracking down compiler warnings.
 
+== LayoutTests ==
+
+To run the layout tests you need to have built your WebKitGTK+ with the following command:
+
+{{{
+./WebKitTools/Scripts/build-webkit --gtk
+}}}
+
+To run the tests you need to setup your environment, so that the sizes for fonts and widgets match - the render dumps are compared textually, and the sizes must match for the tests to pass. This means you need to install the Ahem true type font, and also guarantee the following output for fc-match:
+
+{{{
+$ fc-match Times
+n021003l.pfb: "Nimbus Roman No9 L" "Regular"
+$ fc-match Sans-Serif
+Vera.ttf: "Bitstream Vera Sans" "Roman"
+$ fc-match Serif
+VeraSe.ttf: "Bitstream Vera Serif" "Roman"
+$ fc-match Mono
+VeraMono.ttf: "Bitstream Vera Sans Mono" "Roman"
+}}}
+
+This usually means installing the gsfonts-x11 and ttf-bitstream-vera packages in a Debian system. You also need to run the tests inside an X server that has no GTK+ theme set. Xvfb is recommended. So you would do something similar to this:
+
+{{{
+$ Xvfb -ac :23&
+$ env -i DISPLAY=:23 ./WebKitTools/Scripts/build-webkit --gtk --no-launch-safari
+}}}
+
+Never mind the 'safari' in there. It's just inheritance from the past, when Mac was the only 'port'.
+
 == Optimization ==