(Resending as I replied to Allan in private by mistake)) On Friday 06 February 2015 00:15:48 you wrote: [snip] > > 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 understand). > 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 http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
