The problem here is that the source you have downloaded is for building a completely static version of QtWeb.
That means that the Makefile (generated by qmake) wants to build Webkit from source rather than dynamically link to the webkit which is built into our QT (libqtwebkit4). Without an in-depth knowledge of QT project building you are going to find this very difficult to build from source. The qupzilla app is different because the project is set up dynamically link to the Webkit lib provided by the distro.
One possible way you could get around this is to see if the statically linked binary they provide works and if does you could package it that way (this is how we do firefox for example).
That binary works beautifully. Initially my idea was to just package that binary and the license file with it as a sort of "Hello World" example to packaging.
But I got distracted when I saw it create some directories where the binary exists. These are for settings and cache etc.
My thinking then went thus :
- The binary shall be installed, probably to /usr/bin but where will the temporary or user specific settings reside?
So I thought trying to package source may help.
The level of knowledge needed seems to be pretty high.
In order to get thing going I will probably have to get the whole Qt and WebKit source code, place them in some appropriate directory and then run the build from a suitably modified .spec file.
Lots more of reading to come.