From: "Eric Bénard" <eric@eukrea.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qt4: fix generated sdk
Date: Sat, 10 Sep 2011 11:59:30 +0200 [thread overview]
Message-ID: <4E6B3502.6020702@eukrea.com> (raw)
In-Reply-To: <CAP9ODKoUZfRLHDv7p=wJAczZ_nh-7LeETabwzM8X_Hp_EyqN7g@mail.gmail.com>
Hi Otavio,
Le 10/09/2011 11:56, Otavio Salvador a écrit :
> On Sat, Sep 10, 2011 at 06:25, Eric Bénard<eric@eukrea.com> wrote:
>> - qt4-tools-nativesdk : actually the qmkae binary which gets installed
>> comes from the native recipe. This patch fix this problem by laucnhing
>> configure twice : once to compile qmake using the right toolchain for
>> nativesdk, and a second time using the native qmake to compile all the
>> other tools for the nativesdk. Then we install the right qmake.
> ...
>> - toolchain_create_sdk_env_script_append : we need to add OE_QMAKE_CFLAGS,
>> OE_QMAKE_CXXFLAGS and OE_QMAKE_LDFLAGS else the sdk won't find these
>> variables that are inserted by qmake in the Makefiles.
>>
>> - with this patch, oe-core generates a working meta-toolchain-qte which
>> can compile a small example and is properly recognized by qtcreator (this
>> brings oe-core's meta-toolchain-qte to oe-dev's functional state).
> ...
>
> In this case we most probably can drop the qt.conf file from the SDK
> directory, don't we?
>
no qt.conf gets installed in the sdk.
Eric
next prev parent reply other threads:[~2011-09-10 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 9:25 [PATCH] qt4: fix generated sdk Eric Bénard
2011-09-10 9:56 ` Otavio Salvador
2011-09-10 9:59 ` Eric Bénard [this message]
2011-09-10 10:03 ` Otavio Salvador
2011-09-10 10:31 ` Otavio Salvador
2011-09-13 5:44 ` Eric Bénard
2011-09-13 14:12 ` Otavio Salvador
2011-09-13 14:44 ` [PATCH v2] " Eric Bénard
2011-09-16 16:57 ` Richard Purdie
2011-09-16 17:09 ` Otavio Salvador
2011-09-16 19:52 ` Eric Bénard
2011-09-13 17:25 ` [PATCH] " Paul Eggleton
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=4E6B3502.6020702@eukrea.com \
--to=eric@eukrea.com \
--cc=openembedded-core@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.