From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Putting qtwebkit on a diet
Date: Fri, 1 Dec 2017 16:06:30 +0100 [thread overview]
Message-ID: <20171201160630.392cc220@windsurf.lan> (raw)
In-Reply-To: <7264cc95-a3cd-a416-de49-cf06fe865ef1@petroprogram.com>
Hello,
On Fri, 1 Dec 2017 16:51:37 +0200, Stefan Fr?berg wrote:
> I guess on non-ARM the optimize for size feature is doing just? -Os but
> on ARM it also needs thumb enabled.
> Otherwise it nags "Not supported ARM architecture" (this while building
> for raspberry pi3)
Then we don't want additional options for this, because we already have
top-level options to select Thumb2 and -Os.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-01 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 22:12 [Buildroot] Putting qtwebkit on a diet Stefan Fröberg
2017-11-29 23:49 ` Stefan Fröberg
2017-11-30 8:02 ` Thomas Petazzoni
2017-12-01 14:05 ` Stefan Fröberg
2017-12-01 14:10 ` Thomas Petazzoni
[not found] ` <7264cc95-a3cd-a416-de49-cf06fe865ef1@petroprogram.com>
2017-12-01 15:06 ` Thomas Petazzoni [this message]
2017-12-02 1:12 ` Stefan Fröberg
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=20171201160630.392cc220@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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