From: Tasslehoff Kjappfot <tasskjapp@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Qt5
Date: Tue, 26 Feb 2013 12:34:36 +0100 [thread overview]
Message-ID: <512C9DCC.4050005@gmail.com> (raw)
In-Reply-To: <20130222222611.GB3300@jama>
On 02/22/2013 11:26 PM, Martin Jansa wrote:
> On Thu, Feb 21, 2013 at 03:19:45PM +0100, Tasslehoff Kjappfot wrote:
>> Is the meta-qt5 layer at https://github.com/meta-qt5 a work in progress,
>> or should it be usable in its current state?
>
> Not really, but I plan to work on it next week(s).
>
>> I currently use qt4-embedded and compile and sdk with qt-support, and
>> want to try out qt5. Compiling qtbase gave me some packages I can add to
>> my image, but when I tried to create an SDK I got stuck. The
>> files/recipes in meta-qt5 differ so much from todays qt4-stuff that I'm
>> not sure where to begin, but I suspect at least an SDK-recipe/task and
>> maybe some qt5-embedded recipes will have to be added?
>
> upstream sources also differ a lot, so recipes will stay different to
> reflect that.
>
>> Thought maybe I'd see if I can create these recipes, but I just wanted
>> to check if that is the plan forward.
>
> If you create something useable send it as pull request on github, I
> plan to fix issues in current recipes, but don't plan to work on sdk
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
Will do, thanks for the info.
- Tasslehoff
prev parent reply other threads:[~2013-02-26 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 14:19 Qt5 Tasslehoff Kjappfot
2013-02-22 22:26 ` Qt5 Martin Jansa
2013-02-26 11:34 ` Tasslehoff Kjappfot [this message]
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=512C9DCC.4050005@gmail.com \
--to=tasskjapp@gmail.com \
--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