[Development] Modules in qtbase (was: Re: new "debugsupport" module and API)
frederik.gladhorn at digia.com
Tue May 13 18:42:30 CEST 2014
Tirsdag 13. mai 2014 06.23.46 skrev Kalinowski Maurice:
> > >The rest of the libraries in qtbase are really base stuff.
> > Actually I was thinking about splitting a few more things out. In addition
> > to
the ones mentioned above, I believe we would benefit from splitting
> > QtNetwork out into it’s own module. The reason is that QtNetwork is
> > responsible for many of the failing CI runs due to the inherent
> > instability on the network tests. Splitting out the module should help
> > make many of the qtbase integrations go more smoothly.
> > From what I can see nothing else in qtbase (apart from the bearer
> > plugins)
> > depends on qtnetwork, so a split should be possible.
> What about modules depending on qtbase in general? We have had quite many
> case where a change in qtbase caused e.g. qtdeclarative to not work anymore
> and CI for those modules are blocked then. Unfortunately the delay until
> developers recognized that can easily cause 1-2 days of delay. Splitting
> qtbase might increase this case, either for qtnetwork integration
> misbehaving after changes in qtbase, but also for modules depending on
> Comparing those two situations, do you think it's a better trade for moving
> network out?
I think the problem of dependent modules should be solved in a different way.
I've been pushing for quite a while to have nightly builds of all modules in
the CI so we'll get notified when something breaks. So imho the problem is
that we don't build some of the modules until they get a patch or there's
going to be a release.
Hopefully this will be changed really soon now... the last blocker seems
actually just the publishing of the results, everything else is in place.
> Development mailing list
> Development at qt-project.org
Senior Software Engineer - Digia, Qt
Visit us on: http://qt.digia.com
More information about the Development