From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Meta-qt5 sdk
Date: Wed, 27 Nov 2013 22:44:40 +0100 [thread overview]
Message-ID: <20131127214440.GR2870@jama> (raw)
In-Reply-To: <548EF836-E57E-42CC-8E0A-0D77045DE0AE@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
On Wed, Nov 27, 2013 at 09:26:37PM +0100, Simone wrote:
> Hello to all,
> I'm new to this mailing list.
>
> I'm writing because i want to ask the actual status of meta-qt5 layer.
> Actuallly, we are able to build qt5 with examples for our fsl based platform.
> The problem is that, compared to qt4, there is no meta-toolchain-qt5 available.
> The problem is how to configure host system (development pc with qtcreator) for cross compiling application and deploy/debugging them to remote ARM target.
>
> As for qt4, it would be necessary the famous toolchain that contain all libraries, paths and links for qt5, to cross develop application for arm target.
>
> Is this job planned to do by someone?
> If not, there is an alternative solution (maybe documented) to configure qtcreator manually?
>
> I think it would be very useful also for a lot of other people.
Yes it would, please check
https://github.com/meta-qt5/meta-qt5/wiki/SDK
and test/review proposed solution.
--
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-11-27 21:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 20:26 Meta-qt5 sdk Simone
2013-11-27 21:44 ` Martin Jansa [this message]
2013-11-28 21:00 ` Simone
2013-11-30 22:29 ` Otavio Salvador
2013-12-01 12:31 ` Simone
2013-12-01 17:07 ` Eric Bénard
2013-12-01 17:57 ` Dominik Holland
2013-12-09 6:56 ` Marco
2013-12-09 9:20 ` Simone
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=20131127214440.GR2870@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.