[webkit-qt] Debugging QtWebKit on S60 devices through Carbide

[Jocelyn Turcotte]

Hi,

as some of you might have noticed, trying to compile WebKit with 
debugging information for S60 using RVCT will result in armlink crashing 
out of memory.

Lars did some hacking around source files two weeks ago and he was able 
to complete a debug build by compiling multiple .cpp files at once to 
reduce the total size of object files to link. Proper debugging of 
WebKit on the device through Carbide is then now possible.

You can get a python script that achieve the same process from the 
QtWebKit tool git repository that will get the list of sources generated 
by qmake, create aglomerate source files which include other source 
files and tell raptor to compile these files instead (abld is currently 
not supported)

How you can get similar results:
- Get a clone of http://gitorious.org/qtwebkit/tools ( git clone 
git://gitorious.org/qtwebkit/tools.git qtwebkit-tools)
- Initialize the build normally using qmake or running perl 
WebKitTools\Scripts\build-webkit --debug
- Run the debug-webkit-patch-sbsv2.py script from tools clone in your 
WebKit directory
- sbs -c armv6_udeb -j4

The script contains a list of files that should be compiled alone to 
prevent duplicate static symbols definition or includes of incompatible 
headers. It also tries to limit the number of files that gets compiled 
together since if the file gets too big, it's armcc that start crashing 
for non-obvious reasons. So if you have problems with a specific file 
that don't want to compile, you may be able to make it work by hacking 
the script.

If the script allow stable and useful enough results it might be nice to 
later call it automatically from build-webkit.

Jocelyn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-qt/attachments/20100225/63c63b40/attachment.html>