Bug 37211
| Summary: | [Qt] QtWebKit-2.0 needs to install a .prf file and add itself to the QTLIB, QT_CONFIG, and etc. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Rodrigo Belem <rclbelem> |
| Component: | Tools / Tests | Assignee: | Rodrigo Belem <rclbelem> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | ademar, diegohcg, hausmann, jturcotte, kenneth, kristian.amlie, laszlo.gombos, tonikitoo |
| Priority: | P2 | Keywords: | Qt |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Rodrigo Belem
The QtWebKit-2.0 (as a standalone package) needs to tell to qt where it is installed, its dependencies and that it is a qt lib, so it is possible for qt applications to add "QT += webkit" in the .pro files.
Currently it is hard-coded in the following files.
qt-src/mkspecs/qconfig.pri -> line 5
qt-src/mkspecs/features/qt.prf -> lines 39, 69
qt-src/mkspecs/features/symbian/qt.prf -> line 33
It is needed to take this responsibility to QtWebKit.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jocelyn Turcotte
The mechanism we want to use for 2.0 is to install over Qt's own install directory if you want the Qt += webkit syntax in your application's pro file.
Developers wanting to build against a QtWebKit outside of Qt's SDK can use INCLUDE+=... and LIBS+=... (though this is currenly tedious because of different binary file names on Windows)
One of the constraints why its difficult for QtWebKit to take responsibility of this is that qmake is bound to the SDK where it resides and that it is not clear which QtWebKit should be used when Qt += webkit is encountered.
The mechanism to compile Qt modules outside of Qt's source tree is still undetermined and should be looked at in the near future releases of Qt.
Until then we wanted to keep it simple for QtWebKit.
Kenneth Rohde Christiansen
Belem, are you working on this?
Rodrigo Belem
(In reply to comment #2)
> Belem, are you working on this?
I started to work on it and I made some changes to the qt prf files to support the possibility of adding an "external" qt module, but stopped to work on other stuff and I do not know if the qt guys have interest in this feature.
Simon Hausmann
(In reply to comment #3)
> (In reply to comment #2)
> > Belem, are you working on this?
>
> I started to work on it and I made some changes to the qt prf files to support
> the possibility of adding an "external" qt module, but stopped to work on other
> stuff and I do not know if the qt guys have interest in this feature.
I don't think we want external module support right now. We need to get the module support "inside" working first :)
Removing from release blocker.
Laszlo Gombos
+Kristian. Is this bug obsoleted by the work at BUG 53916 ?
Kristian Amlie
(In reply to comment #5)
> +Kristian. Is this bug obsoleted by the work at BUG 53916 ?
Yes.
Ademar Reis
(In reply to comment #6)
> (In reply to comment #5)
> > +Kristian. Is this bug obsoleted by the work at BUG 53916 ?
>
> Yes.
Closing as duplicate then.
*** This bug has been marked as a duplicate of bug 53916 ***