Making it Build
Hello fellow Haiku’ers, as promised I’m posting a quick update on my WebKit / WebPositive contract work. It’s been a little more than a week already, and a small report is due!
Welcome WebKit r115944 ! As you may know, WebKit is a really big project, in the last two years, 70000 revisions have passed and the file count has almost doubled. The approach I took was to start by checking out a recent WebKit revision and try building the components one by one, re-applying our changes. The idea was to add only the strict necessary for Haiku and at the same time try to include as many features as possible, ignoring assumptions and workarounds that aren’t needed anymore. As many things have changed in WebKit and as I needed to get familiar with this huge codebase anyway, I decided to dismantle our port and put it back together again, like one would have done with a complex piece of mechanics. Thus I did a Jamfile from scratch, based on other platforms buildsystems, and replayed our changes one by one, as the compiler asked. Each time trying to document my changes and research the reasons and implications of the changes.
WebKit is composed of several distinct parts, as seen in the source tree:
WTF (Web Template Framework) provides base utility classes for all the project, it’s pretty much platform agnostic and only few changes were needed to make it build again. It took me a day to get it to build again on Haiku.
old current Richards: 784 5295 DeltaBlue: 726 4483 Crypto: 463 5305 RayTrace: 1985 8026 EarleyBoyer: 1803 6355 RegExp: 1121 2593 Splay: 2430 6723 NavierStokes: 780 4242 ---- Score (version 7): 1091 5124
Next is WebCore, where the real meat is. This one took me around ten days (yes, I had already started before posting my contract proposal, if only to estimate the work needed) to get it in back a buildable state, following the same approach, trying to understand even the smallest change. I have no way to test if it behaves as expected yet, but I’m at least confident that I haven’t devied too much functionally-wise. I’ll get back to it when I have a browser to play with!
And now the WebKit part, which mainly contains the client API to build browsers, HaikuLauncher test application and WebPositive sources (that will be moved in the Haiku source tree at some point). It contains some fat classes, but it’s not as heavy as WebCore and when that one builds I’ll be finished with this first phase of ‘Making it Build’.
You can follow my progress on my github repository https://github.com/aldeck/haikuwebkit (more a personal backup than a real collaborative repository as it’s a git-svn clone of our current haiku-webkit svn repository)
Hope you enjoyed this piece of text, I’m for one really enjoying working on this project :-)
Best regards, Alex
- [GSoC 2017] Porting Swift to Haiku - Week #4 #5
- [GSoC2017: Harfbuzz] Report #3
- [GSoC 2017] Preferences GUI Refactoring - Weekly Report 3
- [GSoC 2017] Calendar Application: Weekly Report 3
- [GSoC 2017] 3D Hardware Acceleration - Weekly Report 3
- [GSoC 2017 - BTRFS Write Supports] Week #4 #5
- [GSoC 2017] Preferences GUI Refactoring - Weekly Report 2
- [GSoC 2017] Porting Swift to Haiku - Week #3
- Haiku monthly activity report - 05/2017