On Thursday 07 January 2016 19:59:30 Dmitry Shachnev wrote:
> Hi,
>
> As you already know, in Qt 5.6 there was a change in ELF versions, from
> @Base to @Qt_5. I have developed a script for that (migrate-symbols.py)
> that scans the build log and updates the symbols files accordingly. That
>
Hi,
As you already know, in Qt 5.6 there was a change in ELF versions, from @Base
to @Qt_5. I have developed a script for that (migrate-symbols.py) that scans
the build log and updates the symbols files accordingly. That script changed
the ELF version tags, but it did not touch the package
On Thursday 07 January 2016 19:59:30 Dmitry Shachnev wrote:
> Hi,
>
> As you already know, in Qt 5.6 there was a change in ELF versions, from
> @Base to @Qt_5. I have developed a script for that (migrate-symbols.py)
> that scans the build log and updates the symbols files accordingly. That
>
On Thu, Jan 07, 2016 at 09:18:16PM +0100, Pino Toscano wrote:
>> But thinking more about this, maybe bumping the versions is really a
>> better solution.
>
> Yes, it is.
You are right. Thanks! Done in [1].
To Lisandro or whoever will be updating other Qt modules to 5.6: I have now
added an
On Thursday 07 January 2016 21:18:16 Pino Toscano wrote:
> In data giovedì 7 gennaio 2016 22:49:24, Dmitry Shachnev ha scritto:
> > Hi Pino,
> >
> > On Thu, Jan 07, 2016 at 08:19:03PM +0100, Pino Toscano wrote:
> > > @Qt_5 symbols need to require version >= 5.6.0~beta, then: if not, the
> > >