From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Qt5
Date: Fri, 22 Feb 2013 23:26:11 +0100 [thread overview]
Message-ID: <20130222222611.GB3300@jama> (raw)
In-Reply-To: <51262D01.7070601@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
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
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-02-22 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 14:19 Qt5 Tasslehoff Kjappfot
2013-02-22 22:26 ` Martin Jansa [this message]
2013-02-26 11:34 ` Qt5 Tasslehoff Kjappfot
-- strict thread matches above, loose matches on Subject: below --
2019-05-25 6:00 qt5 Vahid Gharaee
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=20130222222611.GB3300@jama \
--to=martin.jansa@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 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.