From: Christian Gagneraud <chgans@gna.org>
To: yocto@yoctoproject.org
Subject: Re: Yocto Project 1.5_M5.rc6
Date: Fri, 11 Oct 2013 15:08:03 +1300 [thread overview]
Message-ID: <52575D83.9010405@gna.org> (raw)
In-Reply-To: <CAP9ODKooi3-gBELD86fsipqc98FCJt_jMPBNjd9gndaZjpefMw@mail.gmail.com>
On 11/10/13 14:55, Otavio Salvador wrote:
> On Thu, Oct 10, 2013 at 10:45 PM, Saul Wold <sgw@linux.intel.com> wrote:
>>
>> Sorry for the top post here. The real reason we still have Qt3 is because
>> it's required part of the LSB spec. OE-Core contains Qt4 and we know that
>> meta-qt5 exists from Otavio and Martin.
>>
>> I know that Richard and Paul have been watching what's going on with
>> meta-qt5.
>
> The biggest missing feature at meta-qt5 is the lacking of toolchain
> support; I am still looking for someone to sponsor me to work on this
> (as it is not a small task), a critical need from my side for it or
> someone step on and do it :)
Yes, and ideally it would be nice if this toolchain would be easy to use
with QtCreator.
Some weeks ago, I had a look at writing a Yocto plugin for QtCreator
(using Danny/Qt4), and the biggest problem was how you "activate" the
toolchain, sourcing the env setup is good when you work in a shell, but
it would be better if the toolchain comes with a machine friendly
manifest file, this would allow as well to use several yocto toolchains
(eg, for different architectures/machines) from within QtCreator.
My 2 cents.
Chris
next prev parent reply other threads:[~2013-10-11 2:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 22:35 Yocto Project 1.5_M5.rc6 Flanagan, Elizabeth
2013-10-10 21:37 ` Christian Gagneraud
2013-10-10 22:02 ` Jeff Osier-Mixon
2013-10-10 22:26 ` Christian Gagneraud
2013-10-11 0:01 ` Otavio Salvador
2013-10-11 0:31 ` Jeff Osier-Mixon
2013-10-11 1:45 ` Saul Wold
2013-10-11 1:55 ` Otavio Salvador
2013-10-11 2:08 ` Christian Gagneraud [this message]
2013-10-14 15:36 ` Georgescu, Alexandru C
2013-10-11 1:56 ` Christian Gagneraud
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=52575D83.9010405@gna.org \
--to=chgans@gna.org \
--cc=yocto@yoctoproject.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.