[Development] Deprecating modules with 5.5

Lisandro Damián Nicanor Pérez Meyer perezmeyer at gmail.com
Fri Feb 6 02:21:26 CET 2015

(Resending as I replied to Allan in private by mistake))

On Friday 06 February 2015 00:15:48 you wrote:
> > But at least there we could just disable JIT, which is what we did. When
> > we
> > had V8 around (if I remember correctly it was used for QML, but my memory
> > might be failing me) we couldn't.
> The problem with PowerPC was that the non-JIT fallback was not working on
> big endian machines, which was not discovered by any of the regularly
> tested platforms and configurations. I meant it as an example that having a
> non-JIT fallback doesn't seem to help much because so few people use it
> that it is not even discovered when it compiles but crashes on run.

Again, true. The good thing here is that, thanks a lot to your help, it was 
traced down and fixed. With V8 we don't have that chance (as far as I 

> About QtWebEngine, do you know what system libraries you have problems with
> it duplicating? I think we can configure most of it in the build system and
> already follow the Qt build settings for some that are usually shipped with
> Chromium.

The real answer is simple: all of them. We do our best to avoid embedded 
libraries (and yes, we sometimes fail to do it, and that's a bug for us).

If I where to start at some place I would choose V8 and ffmpeg, but the real 
thing is simply all of them.

Lisandro Damián Nicanor Pérez Meyer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20150205/9c918f9b/attachment.sig>

More information about the Development mailing list