[Development] 32bit linux build of qt5.10.0 w/ webengine

[Toan Pham]

Thiago,

I managed to get the build completed by performing these steps:

  1.  Followed your advise on enabling sse2 because it is a
hard-requirement.
  2.  Patched libvpx heavily to disable avx+avx2/sse3+ (see attached patch)
  3.  Patched libyuv (see attached patch)
  4.  Patched qwebengine/src/core/Makefile.gn_run to launch ninja in single
thread - otherwise build w/ terminate by Out-Of-Memory manager.
  5.  Used 32bit native linker even though you recommended a 64bit linker.

Step# 2 and 3 were needed because the compiler I was using was optimized
for pentium4, it wouldn't be able to compile/link-in SIMD instructions
beyond SSE2.


After all that hard work, minimal webengine browser (located at
qtwebengine/examples/webengine/minimal) did not show anything when I
launched it (see attached screenshot).  I also launched the same browser
which worked fine under lxc-ubuntu16.04-32bit; but did not show anything
within the chroot environment of the pentium4 build.  OnPageLoad event of
qtwebengine showed that webpage loaded successfully; so it made me to
believe that this is an issue with qwebenginewidget.  FYI, within the same
build environment, I was able to run QtWebKit from Qt-5.x a few months
back.  Please help if you know what possibly happened to qwebengineview not
rendering anything on the view.


Thank you,

TP




On Mon, Jan 8, 2018 at 3:21 AM, Lars Knoll <lars.knoll at qt.io> wrote:

> >
> >> For me, it's quite simple:
> >> No (opensource/commercial) Qt CI = No (opensource/commercial) Qt
> >> binaries = No (opensource/commercial) support.
> >
> > No CI, see above.
> > No binaries, build from sources.
> > No support, sorry, I can't comment.
>
> Just a quick comment from TQtC’s perspective on this: We do commercially
> support more platforms than we create binaries for. Linux/32bit is
> certainly one of those.
>
> But as Thiago pointed out, those platforms are not always tested quite as
> well (unfortunately we can’t possibly test all combinations of OS/CPU
> architecture/distribution in our CI).
>
> Cheers,
> Lars
>
> >
> >> If you don't build and test on a regular basis, it can break at any
> >> moment without anyone noticing (and it did happened at least once)
> >
> > You're right, but given all the other permutations, we're very likely
> covered
> > at a good 99% certainty.
> >
> >> PS: In case you think I'm ranting for free here, i would like to say
> >> (again) that I think Qt is a great piece of (opensource/commercial)
> >> SW, and big thumb up to anyone behind this, The Qt Project, The Qt
> >> Company, Intel, ICS, KDAB, KDE, ... and everyone else, individual or
> >> corporate.
> >
> > We're having a constructive conversation, don't worry.
> >
> > --
> > Thiago Macieira - thiago.macieira (AT) intel.com
> >  Software Architect - Intel Open Source Technology Center
> >
> > _______________________________________________
> > Development mailing list
> > Development at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20180111/610ba157/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qwebengine.pentium4-5.10.0.patch
Type: text/x-patch
Size: 39980 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20180111/610ba157/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: desk0.png
Type: image/png
Size: 238481 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20180111/610ba157/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: desk1.png
Type: image/png
Size: 211171 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20180111/610ba157/attachment-0001.png>