All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Kepplinger <martin.kepplinger@ginzinger.com>
To: buildroot@busybox.net
Subject: [Buildroot] why qt5webengine dependencies?
Date: Fri, 15 Mar 2019 08:17:55 +0100	[thread overview]
Message-ID: <df4c4c02-da91-69ab-9e28-6226db717bc7@ginzinger.com> (raw)
In-Reply-To: <20190313003348.04cdc397@gmx.net>

On 13.03.19 00:33, Peter Seiderer wrote:
> Hello Martin,
> 
> On Tue, 12 Mar 2019 11:21:07 +0100, Martin Kepplinger <martin.kepplinger@ginzinger.com> wrote:
> 
>> hi Gael,
>>
>> why does qt5webengine in buildroot have a dependency on
>> * udev:
>> I apply the following patch and create /dev/shm at runtime, which works
>> out just fine. At least a build-depencency is questionable, isn't it?
>> --- a/src/core/config/linux.pri
>> +++ b/src/core/config/linux.pri
>> @@ -8,7 +8,7 @@ gn_args += \
>>      use_gnome_keyring=false \
>>      use_kerberos=false \
>>      linux_use_bundled_binutils=false \
>> -    use_udev=true \
>> +    use_udev=false \
>>      use_bundled_fontconfig=false
>>
> 
> - Because it is the default?
> - Why do you want to do this/change the default? Saving one small udev package
> for an huge package as qt5webengine (loosing hot-plugging support for keyboad/mouse)?
> 

nevermind, udev is fine (as long as it's not gudev :) and if people
really don't use it, they can work around it.

>>
>> * OpenGL backend:
>> I'm yet to test this, but Qt webengine semms to support building with
>> "no-opengl" since 5.8! And there's QT_WEBENGINE_DISABLE_GPU at runtime,
>> so...
> 
> The QT_WEBENGINE_DISABLE_GPU option seems to be run time (and not compile time)
> option...
> 
> And yes [1] mentions Rendering without GPU:
> 
>   In a number of scenarios, we disable using the GPU (e.g. when using ANGLE on
>   Windows or if the OpenGL driver is known to have problems). In this case,
>   the GPU thread will not be initialized at all and the renderer processes will
>   use Skia's software rasterizer to generate bitmaps that are copied to the browser
>   process using shared memory. In this case, Qt WebEngine will create copies of these
>   bitmaps and use them to generate QImages, which are then used to create QSGTextures.
>   This happens during the creation of scene graph nodes in DelegatedFrameNode::commit.
>   The code that does the actual copying can be found in ResourceHolder::initTexture.
> 
> And there are some '#ifndef QT_NO_OPENGL' in the source code, e.g.
> qt5webengine-5.12.1/src/webenginewidgets/render_widget_host_view_qt_delegate_widget.cpp
> 
> Maybe try without OpenGL and submit a patch lifting the requirements (since [1] qt quick
> for qt latest does not depend on opengl in buildroot)?
>  

just to keep you updated, I'm looking into that as part of this
bugreport: https://bugreports.qt.io/browse/QTBUG-54327 and the bottom
line is Qt 5.11 indeed seems to have the opengl dependency lifted already.

I haven't yet figured out how to build without small but nasty
config-patches though... (But with those, I'm running a webengine
browser on imx6ul without mesa3d/khr opengl libs just fine.) but I have
to say I'm not a Qt developer *at all*.

thanks so far,
                       martin


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3616 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190315/1ddf95b9/attachment-0001.bin>

      reply	other threads:[~2019-03-15  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 10:21 [Buildroot] why qt5webengine dependencies? Martin Kepplinger
2019-03-12 15:53 ` Martin Kepplinger
2019-03-12 23:33 ` Peter Seiderer
2019-03-15  7:17   ` Martin Kepplinger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=df4c4c02-da91-69ab-9e28-6226db717bc7@ginzinger.com \
    --to=martin.kepplinger@ginzinger.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.