From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-09
Date: Tue, 11 Nov 2014 14:03:17 +0100 [thread overview]
Message-ID: <20141111140317.18f56b7e@free-electrons.com> (raw)
In-Reply-To: <5461FCCA.1000306@imgtec.com>
Dear Vicente Olivert Riera,
On Tue, 11 Nov 2014 12:10:50 +0000, Vicente Olivert Riera wrote:
> Do you remember when we talked about finding which architectures support
> BR2_PACKAGE_QT_SCRIPT to create a new
> BR2_PACKAGE_QT_ARCH_SUPPORTS_SCRIPT in order to differentiate them from
> BR2_PACKAGE_QT_ARCH_SUPPORTS_WEBKIT? Because BR2_PACKAGE_QT_SCRIPT
> builds fine for MIPS64 n32, but it depends on
> BR2_PACKAGE_QT_ARCH_SUPPORTS_WEBKIT. So, if you disable
> BR2_PACKAGE_QT_ARCH_SUPPORTS_WEBKIT for MIPS64 n32 then you will be
> disabling BR2_PACKAGE_QT_SCRIPT as well. That's why few months ago I
> wanted to disable only BR2_PACKAGE_QT_WEBKIT for MIPS64 n32, but then
> you told me "Hey, there is something wrong here! We need to know which
> architectures support qt-script and which ones support qt-webkit".
Well, then why don't you create BR2_PACKAGE_QT_ARCH_SUPPORTS_SCRIPT ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-11 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-09 Thomas Petazzoni
2014-11-10 7:48 ` Baruch Siach
2014-11-10 15:53 ` Vicente Olivert Riera
2014-11-10 15:58 ` Vicente Olivert Riera
2014-11-10 18:16 ` Thomas Petazzoni
2014-11-11 12:10 ` Vicente Olivert Riera
2014-11-11 13:03 ` Thomas Petazzoni [this message]
2014-11-11 13:34 ` Vicente Olivert Riera
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=20141111140317.18f56b7e@free-electrons.com \
--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