From: rscr <rafacrespiramon@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] QtWebEngine on RPI 0 W
Date: Wed, 5 Feb 2020 07:20:39 -0600 (CST) [thread overview]
Message-ID: <1580908839250-0.post@n4.nabble.com> (raw)
In-Reply-To: <20200205141214.075cf5a3@gmx.net>
> Hi again,
>
> I have tested the QtWebEngine with a qt example and I got:
>
> # ./minimal -platform eglfs
> Illegal instruction
>
> Any idea of what could be causing it?
>
>Hard to say without further information..., did your compile
>minimal yourself or did you enable 'BR2_PACKAGE_QT5BASE_EXAMPLES=y'
>and used the one installed as
'/usr/lib/qt/examples/webenginewidgets/minimal/minimal'
>on the target?
I had enabled 'BR2_PACKAGE_QT5BASE_EXAMPLES=y' and I have used the one in
'/usr/lib/qt/examples/webenginewidgets/minimal/minimal'
Result of 'file minimal':
minimal: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically
linked, interpreter /lib/ld-, for GNU/Linux 4.19.0, stripped
I have no problems running other samples like the qtvirtualkeyboard or touch
ones
>Please provide a complete .config (or defconfig) file...
Here my defconfig: cp4_defconfig.cp4_defconfig
<http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>
>Still using buildroot-2019.02.09?
Yes
>Regards,
>Peter
Kind Regards,
Rafa
--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
next prev parent reply other threads:[~2020-02-05 13:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 10:21 [Buildroot] QtWebEngine on RPI 0 W rscr
2020-01-25 16:25 ` Peter Seiderer
2020-01-28 7:41 ` rscr
2020-01-28 7:58 ` Peter Seiderer
2020-01-28 9:43 ` Peter Seiderer
2020-01-30 11:38 ` rscr
2020-01-30 12:02 ` Peter Seiderer
2020-01-30 12:20 ` Peter Seiderer
2020-02-03 12:51 ` rscr
2020-02-05 11:34 ` rscr
2020-02-05 13:12 ` Peter Seiderer
2020-02-05 13:20 ` rscr [this message]
2020-02-05 14:25 ` rscr
2020-02-18 13:52 ` Peter Seiderer
2020-02-20 22:56 ` Peter Seiderer
2020-02-24 12:21 ` rscr
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=1580908839250-0.post@n4.nabble.com \
--to=rafacrespiramon@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox