From: Dominik Holland <dominik.holland@pelagicore.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-qt5][PATCH 0/2] Add nativesdk tools for Qt5 SDK
Date: Mon, 02 Dec 2013 13:10:56 +0100 [thread overview]
Message-ID: <529C78D0.8030902@pelagicore.com> (raw)
Hi all,
i'm the author of the merge-request on github.
The patchset from Denys looks nice. Especially because it cross compiles
the host tools for the SDK_MACHINE which i forgot todo in my patchset.
I think the best way would be a combined version of both patchsets.
Because some of you think my patchset is too complicated i want to
highlight why i added the complicated creation of the qt.conf and the
additional patching of the mkspec files etc.
I didn't tested Denys version but i think it only works if you source
the environment scripts of the SDK before.
As a Qt developer it's the defacto standard to get a SDK which works out
of the box for your projects by just invoking qmake and no need to
source a script before which changes your environment.
To get this done you need to patch the mkspec folder and the qt.conf to
use relative paths instead the hardcoded paths which where created
during the yocto build.
In addition i created a linux-oe-sdk-g++ which contains the real values
of the environment variables but without --sysroot. This will be set by
qt itself by using the CROSS_COMPILE prefix.
I hope you understand that this is really needed if you want to get a
good qt5 integration into a OE SDK.
Best Reagrds
Dominik
P.S. If you want to use the qmake inside qtcreator you would need to set
all the env variable of the environment script inside qtcreator which is
really inconvenient
next reply other threads:[~2013-12-02 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 12:10 Dominik Holland [this message]
2013-12-02 15:56 ` [meta-qt5][PATCH 0/2] Add nativesdk tools for Qt5 SDK Denys Dmytriyenko
2013-12-02 18:46 ` Dominik Holland
-- strict thread matches above, loose matches on Subject: below --
2013-11-26 1:47 Denys Dmytriyenko
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=529C78D0.8030902@pelagicore.com \
--to=dominik.holland@pelagicore.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.