> Yes, that's correct. We need additional functionality that vanilla QtWebKit doesn't have. That's why we use custom version.
At the moment their qtwebkit fork is 28 commits ahead, 39 commits behind qt:dev.
I propose you bundle all of their git submodules inside the source archive and build the libs locally before building PhantomJS. This is sub-optimal but looks like the only way to go.
Hi guys,
here's what upstream says:
> Yes, that's correct. We need additional functionality that vanilla QtWebKit doesn't have. That's why we use custom version.
At the moment their qtwebkit fork is 28 commits ahead, 39 commits behind qt:dev.
I propose you bundle all of their git submodules inside the source archive and build the libs locally before building PhantomJS. This is sub-optimal but looks like the only way to go.