[Development] [Qt5-feedback] 3rdpart platform plugins, tests and CI

Rohan McGovern rohan.mcgovern at nokia.com
Wed Nov 2 00:06:41 CET 2011


Holger Hans Peter Freyther said:
> On 10/31/2011 11:30 PM, Sergio Ahumada Navea wrote:
> 
> > 1) Source Code Management -> Git
> >     URL of repository: git://gitorious.org/qt/qtbase.git
> >     Branch Specifier : master
> 
> 
> > Finally, you can see my build log: http://pastebin.com/iNVph7DP . This 
> > is almost the same that the CI system is doing right now.
> 
> Hi,
> 
> how difficult will it be to only checkout/update/build qtbase and not _all_ of
> Qt? Is this something that is planned?

That is already the way it works - as Shane Kearns pointed out in a
followup mail.  For testing qtbase, you get qt5, qtbase and v8.
For testing another gitmodule, you get just that gitmodule, plus the
gitmodules it depends on, plus qt5.

> E.g. with the creation of separate
> modules declarative/webkit probably should not always require the latest
> version of qtbase.

Currently, each gitmodule has a top-level sync.profile which specifies
the other repositories to be checked out for the test, along with their
SHA1.  Most of them are explicitly opting in to refs/heads/master (or
refs/heads/qml2 for qtquick3d) as it was decided a while back that the
goal should be to have the tip of all modules working together.  So,
yes, although the latest qtdeclarative may not require the latest
qtbase, it's an explicit choice (controllable by the module maintainer)
to test it this way at the moment.



More information about the Development mailing list