From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/3] qt4-tools-sdk: bring compatibility with QTCreator
Date: Thu, 23 Sep 2010 08:32:26 +0200 [thread overview]
Message-ID: <4C9AF47A.4060806@eukrea.com> (raw)
In-Reply-To: <AANLkTimVQEU7wgy5rGjj7bzuACSjRhU8DTp1b92OPVTN@mail.gmail.com>
Le 23/09/2010 03:55, Cliff Brake a écrit :
> On Wed, Sep 22, 2010 at 6:35 PM, Eric Bénard<eric@eukrea.com> wrote:
>> * this links "puts" mkspecs at the place where QTCreator search
>> for it in order to detect a toolchain
>> * thanks to this link QTCreator detects the toolchain generated using
>> meta-toolchain-qte and can cross compile applications without any
>> hack
>
> This is somewhat off-topic, but could you outline the procedure you
> use to create a Qt SDK?
bitbake meta-toolchain-qte
> How does this recipe fit in with meta-toolchain-qte?
>
yes, meta-toolchain-qte -> TOOLCHAIN_HOST_TASK ->
task-qte-toolchain-host -> RDEPENDS qt4-tools-sdk
> Also, have you done remote debugging with QtCreator -- just curious
> how well that works.
>
I'm finalizing the doc (translating it in english and removing the hacks
no morenecessary for libmpfr & libncurses & this mkspecs link once the
patches are in the tree), I'll post a link once it's online (in the
coming weeks).
Eric
prev parent reply other threads:[~2010-09-23 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 22:35 [PATCH 1/3] sdk.bbclass: allow virtclass-sdk override Eric Bénard
2010-09-22 22:35 ` [PATCH 2/3] qt4-tools-sdk: bring compatibility with QTCreator Eric Bénard
2010-09-22 22:35 ` [PATCH 3/3] gdb-cross-sdk: use static libncurses libtinfo libz and libexpat Eric Bénard
2010-09-22 23:00 ` Tom Rini
2010-09-23 1:55 ` [PATCH 2/3] qt4-tools-sdk: bring compatibility with QTCreator Cliff Brake
2010-09-23 6:32 ` Eric Bénard [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=4C9AF47A.4060806@eukrea.com \
--to=eric@eukrea.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.