Merge lp:~autopilot/autopilot-qt/magic-driver-loading-awesomeness into lp:autopilot-qt
Status: | Merged |
---|---|
Approved by: | Juhapekka Piiroinen |
Approved revision: | 44 |
Merged at revision: | 34 |
Proposed branch: | lp:~autopilot/autopilot-qt/magic-driver-loading-awesomeness |
Merge into: | lp:autopilot-qt |
Diff against target: |
354 lines (+170/-67) 13 files modified
autopilot-qt.pro (+7/-2) debian/autopilot-qt.install (+0/-1) debian/autopilot-qt5.install (+0/-1) debian/changelog (+2/-2) debian/control (+12/-17) debian/copyright (+1/-1) debian/libautopilot-qt.install (+1/-0) debian/lintian-overrides (+1/-1) debian/rules (+5/-5) driver/driver.pro (+38/-0) lib/lib.pro (+0/-37) lib/qttestability.cpp (+87/-0) lib/qttestability.h (+16/-0) |
To merge this branch: | bzr merge lp:~autopilot/autopilot-qt/magic-driver-loading-awesomeness |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
PS Jenkins bot | continuous-integration | Needs Fixing | |
Juhapekka Piiroinen (community) | Approve | ||
Omer Akram (community) | Approve | ||
Review via email: mp+142826@code.launchpad.net |
Commit message
autopilot-qt is now a single package with drivers that load correctly for each supported Qt version.
Description of the change
This branch changes the way autopilot-qt works. Instead of creatinbg multiple binary packages for each version of qt, we create a small driver library that links to nothing. This gets loaded by the Qt app the user wants to test. This small library works out which version of Qt the app that loaded it is linked to, and loads the appropriate autopilot driver library.
Things that still need to be done before this branch can merge (mostly packaging stuff):
1) The binary package name should be renamed to 'libautopilot-qt' to make it in line with the gtk plugin.
2) The package ends up depending on all the Qt4 and Qt5 packages - I think this is '${shlibs:Depends}' in action. We don't want that, since it forces users to install Qt5 whenever they're testing a Qt4 app, and vice versa. We can be assured that they have the correct Qt libraries installed anyway, since our driver library was loaded by Qt. So we need to find a way around this - possibly just remove '${shlibs:Depends}' (but then remember to depend on libxpathselect).
3) Currently the driver library (libqt_testability) is built twice - once in the qt4 and once in the qt5 directory. Ideally we'd just build it once.
Over to you....
PASSED: Continuous integration, rev:38 s-jenkins: 8080/job/ autopilot- qt-ci/38/ s-jenkins: 8080/job/ autopilot- qt-ci/. /build= pbuilder, distribution= quantal, flavor= amd64/38/ console
http://
Executed test runs:
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins: 8080/job/ autopilot- qt-ci/38/ /rebuild/?
http://