Bug 37211 - [Qt] QtWebKit-2.0 needs to install a .prf file and add itself to the QTLIB, QT_CONFIG, and etc.
Summary: [Qt] QtWebKit-2.0 needs to install a .prf file and add itself to the QTLIB, Q...
Status: RESOLVED DUPLICATE of bug 53916
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Rodrigo Belem
URL:
Keywords: Qt
Depends on:
Blocks:
 
Reported: 2010-04-07 08:46 PDT by Rodrigo Belem
Modified: 2011-02-28 09:33 PST (History)
8 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rodrigo Belem 2010-04-07 08:46:16 PDT 
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.
Comment 1 Jocelyn Turcotte 2010-04-09 02:05:40 PDT 
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.
Comment 2 Kenneth Rohde Christiansen 2010-05-07 06:14:21 PDT 
Belem, are you working on this?
Comment 3 Rodrigo Belem 2010-05-07 06:25:10 PDT 
(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.
Comment 4 Simon Hausmann 2010-05-07 07:54:30 PDT 
(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.
Comment 5 Laszlo Gombos 2011-02-26 18:15:30 PST 
+Kristian. Is this bug obsoleted by the work at BUG 53916 ?
Comment 6 Kristian Amlie 2011-02-27 23:53:29 PST 
(In reply to comment #5)
> +Kristian. Is this bug obsoleted by the work at BUG 53916 ?

Yes.
Comment 7 Ademar Reis 2011-02-28 09:33:37 PST 
(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 ***