Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: rscr <rafacrespiramon@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] QtWebEngine on RPI 0 W
Date: Mon, 3 Feb 2020 06:51:18 -0600 (CST)	[thread overview]
Message-ID: <1580734278053-0.post@n4.nabble.com> (raw)
In-Reply-To: <20200130132047.5d82cab0@gmx.net>

Dear Peter, 

I have fixed the issue:

- Using the buildroot toolchain with gcc 5.x
- Increasing swap in my Ubuntu host until 10 GB
(https://chromium.googlesource.com/chromium/src/+/master/docs/linux/build_instructions.md#System-requirements) 
- Using BR2_JLEVEL = 2

Now QtWebEngine is built with the image. 

I just have to test if I can run a Qt app with WebEngineView


>Your provided defconfig states:
>
>BR2_TOOLCHAIN_EXTERNAL_PATH="/home/ibercomp/rcr/tools/toolchains/sourceforge/rpi0w/cross-pi-gcc->6.3.0-0"
>
>So you are still not using a buildroot provided toolchain (I suspect from
the path your use
<one from the https://sourceforge.net/projects/raspberry-pi-cross-compilers/
project)?

On the meanwhile, I was trying with some other toolchain because of the
&quot;Virtual exahusted memory&quot; failure I got with the buildroot one.


>BR2_PACKAGE_QT5WEBENGINE is not enabled in the given defconfig, wrong
defconfig?

At first attempt of building an image with a new toolchain, I decided not to
add the QtWebEngine. I just was trying to test if the new toolchain was
worked...and did not.

Kind Regards, 

Rafa







--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

  reply	other threads:[~2020-02-03 12:51 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 [this message]
2020-02-05 11:34               ` rscr
2020-02-05 13:12                 ` Peter Seiderer
2020-02-05 13:20                   ` rscr
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=1580734278053-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