Merge lp:~osomon/oxide/versions into lp:~oxide-developers/oxide/oxide.trunk
Proposed by
Olivier Tilloy
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 1442 | ||||
Proposed branch: | lp:~osomon/oxide/versions | ||||
Merge into: | lp:~oxide-developers/oxide/oxide.trunk | ||||
Diff against target: |
204 lines (+85/-5) 8 files modified
qt/core/api/oxideqglobal.cc (+13/-1) qt/core/api/oxideqglobal.h (+5/-2) qt/core/common/oxide_version.h.in (+23/-0) qt/core/core.gyp (+18/-0) qt/qmlplugin/oxide.qmltypes (+2/-0) qt/quick/api/oxideqquickglobal.cc (+9/-1) qt/quick/api/oxideqquickglobal_p.h (+7/-1) qt/tests/qmltests/api/tst_OxideGlobal.qml (+8/-0) |
||||
To merge this branch: | bzr merge lp:~osomon/oxide/versions | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Chris Coulson | Approve | ||
Review via email: mp+291518@code.launchpad.net |
Commit message
Add a 'version' and a 'chromiumVersion' properties to the Oxide global object.
To post a comment you must log in.
Thanks for this.
My main issue with this is that it leaves a build artefact in the source tree - pre-processed headers should be in the build directory really. It may be non-trivial with the current approach (using cmake to create a header for the core library, configured with gyp) to include a header from the build-directory - you'd probably need to pass an include path to gyp just for this.
It might be better to generate this the same way that chrome_version.h is already generated (from gyp, using third_party/ chromium/ src/build/ util/version. py and having the file in qt/core/common). I just verified that it's possible to re-use Chromium's version.py (qt/VERSION is formatted to work with this already).
I've left a couple of comments inline too.