From: Michael 'Mickey' Lauer <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: qt4 upgrade to 4.7.0-beta1
Date: Sat, 05 Jun 2010 13:25:44 +0200 [thread overview]
Message-ID: <1275737144.1981.0.camel@saphir> (raw)
In-Reply-To: <4C0992ED.6000102@gmail.com>
Am Samstag, den 05.06.2010, 01:57 +0200 schrieb Matthias Günther:
> Hello.
>
> I've been working with QML (Qt Quick) for some time now and therefore
> I've created recipes for Qt 4.7.0-tp and beta1 versions. The patches
> just disable the not cross compiling parts (e.g. some demos/examples).
>
> Should I send the beta1-patch to the ML or is it better to wait for the
> final release?
Feel free to submit it. QML is an amazing technology and I'd love to do
something with it on OE-powered devices.
--
:M:
next prev parent reply other threads:[~2010-06-05 11:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 23:57 qt4 upgrade to 4.7.0-beta1 Matthias Günther
2010-06-05 5:57 ` Koen Kooi
2010-06-05 6:03 ` Martin Jansa
2010-06-05 14:01 ` Matthias Günther
2010-06-05 11:25 ` Michael 'Mickey' Lauer [this message]
2010-06-05 14:10 ` Matthias Günther
2010-06-05 17:08 ` Koen Kooi
2010-06-05 21:15 ` Matthias Günther
2010-06-06 12:09 ` Koen Kooi
2010-06-07 2:05 ` Matthias Günther
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=1275737144.1981.0.camel@saphir \
--to=mickey@vanille-media.de \
--cc=openembedded-devel@lists.openembedded.org \
/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