After much pain and agony, I have finally figured out how to build WebKitQt and QtLauncher (the demo app) on Mac OS X.

It's probably not supposed to be this hard, but there's a dearth of info on how to do this (I suspect because the guys at Trolltech are busy trying to get Qt 4.3 out the door).

In any case, I wanted to use WebKit in a spidering app I'm working on using Qt 4.3 and C++. Even though I am a 100% Mac-based developer these days, I still want my apps to be cross-platform, so I opt for Qt over Cocoa/Objective-C. This meant that I had to follow the Apple/XCode dylib rules as well as install a few libraries that weren't on my system by default.

1 - Using fink, I installed flex and bison (separate installs).
2 - Then I had to specify QTDIR environment variable (QTDIR=/usr/local/Trolltech/Qt-4.3.0beta) (then export QTDIR)
3 - add QTDIR to your PATH environment variable (PATH=$PATH:$QTDIR/bin) (then export PATH)
4 - make sure you have NOT specified a QMAKESPEC in your bash profile (so echo $QMAKESPEC should not return anything)
5 - grab the latest WebKit source using SVN (see webkit.org for instructions)
6 - run ./WebKit/WebKitTools/Scripts/build-webkit

This should make the build script compile using qmake.

7 - copy the dylibs from /WebKit/WebKitBuild/Release/lib to /usr/lib

QtLauncher should now run (located in /WebKit/WebKitBuild/Release/WebKitQt/QtLauncher).

In order to compile/edit this in xcode...

8 - in a terminal window - cd into /WebKit/WebKitQt/QtLauncher/
9 - run the following"qmake -spec macx-xcode"

You should now see QtLauncher.xcodeproj in that directory.

You may have to manually delete and re-add some of the Qt libraries in XCode, as well as adding the QtNetwork.framework, since I don't think it's added by default.

I'm sure I missed some of the details (since I typed this rather quickly), but this captures many of the small steps that tripped me up along the way.

I'm almost done with my Qt 4.3 and WebKit-based Internet spider.

It uses WebKit for webpage retrieval, rendering, and link extraction, and I also created a squarified treemap widget for visualization of different aspects of individual pages and the spidered pages.

Here's a preview...

I just added a new widget to my GameTracker app to track the line of motion relative to the field of view. This is basically a calculation of the player's actual line of motion relative to where they were looking (the player-camera's yaw).

The rotation monitor in the upper right shows a diagnostic view on the yaw vs. pitch information about the player-camera.

The lower right-corner shows a caterpillar view on the player's movement through the game level. The big chart area shows the raw data, and the top-left has a list of the available sessions of data (that have already be cleaned/filtered of bad sessions).

Next, I'll be adding a bunch more statistics to the statistics view.... all of which will be output in a format that I can do post-processing in SPSS.

The major purpose of all this gadgetry is to allow me to tune and trust my calculated variables -- which will become critical when I begin to do statistical analysis on the video game player's navigational behavior.