[oe] [meta-qt5][PATCH 2/2] qtbase: align target qmake paths

[Martin Jansa]

On Thu, Nov 19, 2015 at 02:06:07PM +0100, Andreas Müller wrote:
> On Thu, Nov 5, 2015 at 12:32 AM, Andreas Müller
> <schnitzeltony at googlemail.com> wrote:
> > On Wed, Nov 4, 2015 at 11:54 PM, Martin Jansa <martin.jansa at gmail.com> wrote:
> >> On Wed, Nov 04, 2015 at 06:30:09PM +0100, Andreas Müller wrote:
> >>> With this we can setup qt-creator to build/debug on target again.
> >>
> >> Can we apply this change to qtbase-native and nativesdk-qtbase as well
> >> or will it break things?
> > Have not tested but I don't expect it to work for our cross/sysroot
> > magic: the patch wipes all host/sysroot paths out of (target) qmake.
> >>
> >> With 5.6 I was finally able to use the same patches for target qtbase
> >> and native(sdk) with only:
> >>     file://0008-Always-build-uic.patch \
> >>     file://0009-Add-external-hostbindir-option-for-native-sdk.patch \
> >> included only for native(sdk) that makes my qtbase branches in
> >> github.com/meta-qt5/qtbase a lot easier to maintain.
> > Understood, happy and fully agreed :)
> >>
> >> If it cannot be changed for all, can we make it conditional, e.g.
> >> [ "$QT_CROSS_COMPILE" = "yes" ]
> >> like in new version of:
> >> https://github.com/meta-qt5/qtbase/commit/10283d010d7a66c485cda1e9b1c0cf7c41e358b3
> >>
> > Need a look into but this seems to me the path to take: handling
> > conditionals during build is what configure is made for :)
> >
> > As you might guess: I am using qt-creator on target from time to time
> > for building/debugging simple projects or profiling QML - so I am very
> > interested in qt-creator working on target.
> >
> Hey Martin,
> 
> just saw that you applied this one to jethro-next - please wait with
> applying to jethro. I'll send new versions for master & jethro
> hopefully with same patch content with conditional modification of
> configure and setting linux-g++ as mkspec because linux-oe-g++ on
> target causes trouble.

Don't worry I wasn't planing to merge jethro-next anytime soon, it was
just to store the "jethro" applicable version somewhere until it's
resolved in master, if you send different version for jethro as well
I'll update it there.

But thanks for keeping an eye on me :).

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20151119/c53765a5/attachment-0002.sig>