On Thursday 07 March 2013 13:43:30 Alberto Mardegan wrote: > Hi! :-) > I'm developing the QtQuick2 bindings for WebKit1 (see the mail I sent > just few minutes ago). Indeed, the code and the APIs are not mature (or > even ready) so I don't think it can be merged into QtWebKit anytime soon. > > However, as the QtQuick2 WebKit1 bindinds approach a state which looks > usable to me, I'd actually like to be able to use them from other projects. > > So, I'm wondering if it would make sense to move them into a separate > repository, which could then being built separately from QtWebKit. > So far, I didn't have to modify any code in WebKit, so my plugin should > actually work along with an unmodified version of QtWebKit. > > But in order to build it, I needed to make use of some of the private > headers (such as QWebPageAdaptor). > Given that the corresponding symbols are defined (at least in Ubuntu's > libQt5WebKit.so), do you think it makes sense to distribute private > headers as well?
They are private, thus no. What you could do is something similar to what Qt Creator does (or did? haven't checked since some time): Before you build your WK1 bindings app, define some env var like PATH_TO_WK_SOURCE or similar and then use that to find the private headers. Cheers -- Milian Wolff | milian.wo...@kdab.com | Software Engineer KDAB (Deutschland) GmbH&Co KG, a KDAB Group company Tel. Germany +49-30-521325470, Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-independent software solutions
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ webkit-qt mailing list webkit-qt@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-qt
