Re: [OE-core] weird exports in bitbake.conf

2012-01-04 Thread Phil Blundell
On Wed, 2012-01-04 at 13:49 +, Paul Eggleton wrote: > These are still necessary for building Opie, but I think they really belong > in > palmtop.bbclass in meta-opie, certainly not in oe-core. Unfortunately I just > checked and a bunch of recipes in meta-opie refer to these without inheritin

Re: [OE-core] weird exports in bitbake.conf

2012-01-04 Thread Paul Eggleton
On Wednesday 04 January 2012 12:24:21 Phil Blundell wrote: > There's also a bunch of historical Opie stuff which is currently getting > exported globally: > > export QTDIR = "${STAGING_DIR_HOST}/qt2" > export QPEDIR = "${STAGING_DIR_HOST}" > export OPIEDIR = "${STAGING_DIR_HOST}" > export palmtopd

Re: [OE-core] weird exports in bitbake.conf

2012-01-04 Thread Phil Blundell
On Wed, 2012-01-04 at 12:06 +, Richard Purdie wrote: > On Tue, 2012-01-03 at 17:42 +, Phil Blundell wrote: > > Does anybody know why these vars are exported (or, in the case of > > STAGING_IDLDIR, there at all)? > > > > export QMAKE_MKSPEC_PATH = "${STAGING_DATADIR_NATIVE}/qmake" > > expor

Re: [OE-core] weird exports in bitbake.conf

2012-01-04 Thread Richard Purdie
On Tue, 2012-01-03 at 17:42 +, Phil Blundell wrote: > Does anybody know why these vars are exported (or, in the case of > STAGING_IDLDIR, there at all)? > > export QMAKE_MKSPEC_PATH = "${STAGING_DATADIR_NATIVE}/qmake" > export STAGING_SIPDIR = "${STAGING_DATADIR_NATIVE}/sip" > export STAGING_I

[OE-core] weird exports in bitbake.conf

2012-01-03 Thread Phil Blundell
Does anybody know why these vars are exported (or, in the case of STAGING_IDLDIR, there at all)? export QMAKE_MKSPEC_PATH = "${STAGING_DATADIR_NATIVE}/qmake" export STAGING_SIPDIR = "${STAGING_DATADIR_NATIVE}/sip" export STAGING_IDLDIR = "${STAGING_DATADIR}/idl" p.