[Interest] Qt 5.3 vs Qt 5.4 (etc)
thiago.macieira at intel.com
Tue Jan 20 20:08:10 CET 2015
On Tuesday 20 January 2015 15:30:47 Lisandro Damián Nicanor Pérez Meyer wrote:
> On Tuesday 20 January 2015 08:15:53 Thiago Macieira wrote:
> > On Tuesday 20 January 2015 10:25:04 Lisandro Damián Nicanor Pérez Meyer
> > > If the library is part of Qt itself then it will certainly not hurt, but
> > > nowadays we need to push all Qt submodules at the same time because
> > > there
> > > are runtime checks in order. Ie, I can't just package qtbase 5.3.2 and
> > > push it alone waiting for another submodule like, let's say, qtsvg 5.3.1
> > > to
> > > continue working. This is enforced by Qt itself at runtime.
> > >
> > > But then again, I need to understand it's purpose right first I guess
> > Right, this would be a run-time enforcement of the same exact version.
> Then it shouldn't be a problem (understanding a lib part of Qt, as you only
> replied to that part).
I meant anything using private API (or, at least, triggering the trick). This
is intended for Qt libraries themselves, but it might help you catch mistaken
uses of private API.
Probably QObjectPrivate only.
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Interest