From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt: install QML imports on target
Date: Wed, 27 Feb 2013 20:15:53 +0100 [thread overview]
Message-ID: <512E5B69.7070201@mind.be> (raw)
In-Reply-To: <878v6c859c.fsf@dell.be.48ers.dk>
On 25/02/13 22:15, Peter Korsgaard wrote:
>>>>>> "Daniel" == Daniel Nystr?m<daniel.nystrom@timeterminal.se> writes:
> Daniel> On Wed, Feb 20, 2013 at 11:18 AM, Daniel Nystr?m <
> Daniel>daniel.nystrom at timeterminal.se> wrote:
>
> Daniel> When selecting the Qt declarative module, all the QML imports was
> Daniel> built and installed to staging, but never installed to the target.
>
> Daniel> Signed-off-by: Daniel Nystr?m<daniel.nystrom@timeterminal.se>
>
>
> Daniel> Bumping this patch as I think this is a good candidate for the
> Daniel> 2013.02 release. Currently QtDeclarative is supported by
> Daniel> Buildroot, but the QML imports are not installed to target. The
> Daniel> current imports are:
>
> Daniel> ./QtWebKit/libqmlwebkitplugin.so
> Daniel> ./Qt/labs/folderlistmodel/libqmlfolderlistmodelplugin.so
> Daniel> ./Qt/labs/gestures/libqmlgesturesplugin.so
> Daniel> ./Qt/labs/particles/libqmlparticlesplugin.so
>
> It would be good if someone who knows anything about Qt can ack this
> patch for 2013.02.
Basic QML works without this patch. (Actually, I can't be 100% sure
because the display on my board is currently broken, but at least the
application doesn't report an error when I start it.) So I don't think
this is really needed for 2013.02.
This patch is only necessary if you want to use one of those plugins in
your QML application. I therefore don't agree with always installing
them. There should be a configure option to enable it. Although, maybe
making this 200K installation configurable for a package that already
consumes 15M is perhaps a bit silly... Therefore:
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
(for next)
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
(build-test)
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-02-27 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 10:18 [Buildroot] [PATCH] qt: install QML imports on target Daniel Nyström
2013-02-25 10:31 ` Daniel Nyström
2013-02-25 21:15 ` Peter Korsgaard
2013-02-26 6:23 ` Alexander Lukichev
2013-02-27 19:15 ` Arnout Vandecappelle [this message]
2013-02-27 22:58 ` 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=512E5B69.7070201@mind.be \
--to=arnout@mind.be \
--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