[webkit-qt] Shipping QtWebKit private headers
mardy at users.sourceforge.net
Thu Mar 7 23:11:57 PST 2013
-----BEGIN PGP SIGNED MESSAGE-----
On 03/07/2013 04:53 PM, Milian Wolff wrote:
> On Thursday 07 March 2013 13:43:30 Alberto Mardegan wrote:
>> 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
Thanks for the suggestion, I think I'll end up doing that. However, if
(correct me if I'm wrong) the QWeb*Adaptor APIs are subject to change
from release to release, I see some value in shipping the private
headers. Distributors should be told to put them into a separate
package, something like "qt5webkit-private-dev", so that one could
match the version of that package with the version of the qt5webkit libs.
Otherwise the risk of building with headers which don't match the
symbols exported by the qt5webkit lib is very high.
http://blog.mardy.it <- geek in un lingua international!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the webkit-qt