From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] qt5script: Disable on non-supported platforms
Date: Thu, 26 Dec 2013 23:22:01 +0100 [thread overview]
Message-ID: <20131226232201.2ec1890a@skate> (raw)
In-Reply-To: <1385654237-36389-3-git-send-email-Vincent.Riera@imgtec.com>
Dear Vicente Olivert Riera,
On Thu, 28 Nov 2013 15:57:16 +0000, Vicente Olivert Riera wrote:
> Is the same problem as Qt4 QtScript, it doesn't build because it uses
> JavaScriptCore, so we re-use the existing
> BR2_PACKAGE_QT_ARCH_SUPPORTS_WEBKIT option which already lists which
> platforms are supported by JavaScriptCore.
>
> This is a quick fix. A proposed fix to add support for MIPS64 has
> already been sent to Qt:
>
> https://bugreports.qt-project.org/browse/QTBUG-35191
>
> Fixes:
>
> http://autobuild.buildroot.net/results/231/231c112a3fc18e6cd7d6d10873e22144525c7280/
What is the status of this patch, and the "[PATCH 2/2] qt5quick1:
Disable on non-supported platforms" patch that you sent?
Are they still needed? If so, then it should use a QT5 specific Kconfig
symbol.
Let me know what to do with these patches, so that I can updated their
patchwork status.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-26 22:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 15:57 [Buildroot] [PATCH v3 1/2] qt: Disable QtScript on non-supported platforms Vicente Olivert Riera
2013-11-28 15:57 ` [Buildroot] [PATCH v3 2/2] grantlee: Disable " Vicente Olivert Riera
2013-11-28 21:48 ` Peter Korsgaard
2013-11-28 15:57 ` [Buildroot] [PATCH 1/2] qt5script: " Vicente Olivert Riera
2013-11-28 16:29 ` Thomas Petazzoni
2013-12-26 22:22 ` Thomas Petazzoni [this message]
2013-11-28 15:57 ` [Buildroot] [PATCH 2/2] qt5quick1: " Vicente Olivert Riera
2013-11-28 21:47 ` [Buildroot] [PATCH v3 1/2] qt: Disable QtScript " Peter Korsgaard
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=20131226232201.2ec1890a@skate \
--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 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.