WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
55213
[Qt] Make the WebKit2 build system less confusing for non-Qt developers
https://bugs.webkit.org/show_bug.cgi?id=55213
Summary
[Qt] Make the WebKit2 build system less confusing for non-Qt developers
Andras Becsi
Reported
2011-02-25 05:12:33 PST
Move the WebKit2 API sources from WebKit/qt/QtWebKit.pro into WebKit2/WebKit2API.pri and include that in the final project file to make it easier to localize where to add new sources.
Attachments
proposed patch
(20.12 KB, patch)
2011-02-25 06:10 PST
,
Andras Becsi
no flags
Details
Formatted Diff
Diff
proposed patch v2
(19.21 KB, patch)
2011-02-25 07:14 PST
,
Andras Becsi
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Benjamin Poulain
Comment 1
2011-02-25 05:19:18 PST
That is a good idea. Yesterday, I was lost with the WebKit2 sources being in WebKit/qt/QtWebKit.pro. I think having them in the WebKit2 dir would be far less confusing.
Andras Becsi
Comment 2
2011-02-25 06:10:24 PST
Created
attachment 83798
[details]
proposed patch
Laszlo Gombos
Comment 3
2011-02-25 06:26:33 PST
What about moving these blocks to the existing WebKit2.pri instead of creating yet another build file (WebKit2API.pri) ?
Andras Becsi
Comment 4
2011-02-25 06:35:37 PST
(In reply to
comment #3
)
> What about moving these blocks to the existing WebKit2.pri instead of creating yet another build file (WebKit2API.pri) ?
I think in this case it is more explicit that those sources are the API, and makes it easier to find out where to add new API sources to. But if adding a new file is a problem, I can surely move these blocks to WebKit2.pri, but I think that would make them almost as much hidden as they were in QtWebKit.pro.
Csaba Osztrogonác
Comment 5
2011-02-25 06:43:44 PST
I don't have a strong opinion, WebKit2.pri and WebKit2API.pri are good for me.
Balazs Kelemen
Comment 6
2011-02-25 06:46:49 PST
It is all about not confusing non-Qt guys and WebKit2API.pri speaks for itself so I think it is better.
Andras Becsi
Comment 7
2011-02-25 07:14:24 PST
Created
attachment 83805
[details]
proposed patch v2
Balazs Kelemen
Comment 8
2011-02-25 07:18:39 PST
I won't fight with the Apple guys even more! I would like to go with the first approach.
Csaba Osztrogonác
Comment 9
2011-02-25 07:24:26 PST
After think it over again, adding sources and headers to WebKit2.pri and WebKit2.pro can be confusing for non-Qt developers. But the name of WebKit2API.pri must be obviously for everyone. So that's why I'd like to r+ the first one.
Andras Becsi
Comment 10
2011-02-25 07:37:03 PST
Comment on
attachment 83805
[details]
proposed patch v2 Removing r?, waiting for Ossy.
Benjamin Poulain
Comment 11
2011-02-25 07:42:05 PST
I also prefer having a new file like WebKit2API.pri (maybe the name isn't perfect, WebKit2ApiSource.pri?) WebKit2.pri contains build details that should not be messed with. This file will likely get more and more complicated over time. I think it is cleaner to have a separate file to reference the source files.
Csaba Osztrogonác
Comment 12
2011-02-25 10:00:57 PST
Comment on
attachment 83798
[details]
proposed patch Let's go ahead, r=me.
Csaba Osztrogonác
Comment 13
2011-02-25 10:07:16 PST
Comment on
attachment 83798
[details]
proposed patch Clearing flags on attachment: 83798 Committed
r79690
: <
http://trac.webkit.org/changeset/79690
>
Csaba Osztrogonác
Comment 14
2011-02-25 10:07:25 PST
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug