Re: making qt5 package machine specific

[Martin Jansa <martin.jansa@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]

On Fri, Nov 22, 2013 at 08:40:48AM +0000, André Draszik wrote:
> Hi Martin,
> 
> On Thu, 2013-11-21 at 18:30 +0100, Martin Jansa wrote:
> > Ah one more comment.
> > 
> > qmake5_base.bbclass doesn't look like best place for it.
> > 
> > I guess you have only target qtbase being MACHINE_ARCH, right?
> 
> Everything that was built using the previously configured qtbase, e.g.
> qtwebkit - see below.
> 
> > qmake5_base.bbclass can be inherited by many packages which are
> > TUNE_PKGARCH and don't use (depend) on target qtbase at all, so
> > QMAKE_PACKAGE_ARCH would be used in more recipes then where it's really
> > needed.
> 
> I don't know enough about qmake, but my thinking is that qmake will
> store the (qtbase) configure options somewhere (from the time when you
> configure qtbase for the target), i.e. qmake during the qtwebkit build
> has access to the configuration from the time qtbase was configured.
> Hence the idea is to make all (target) packages that use (inherit)
> qmake5 to use the same PACKAGE_ARCH override.

You can have recipes which use only qtbase-native and qmake only as
build tool and don't use target qtbase at all.

Such recipes inherit qmake5_base to setup paths etc and shouldn't became
MACHINE_ARCH just because target qtbase (which they don't use at all) is.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]