[OE-core] weird exports in bitbake.conf

Phil Blundell philb at gnu.org
Wed Jan 4 12:24:21 UTC 2012


On Wed, 2012-01-04 at 12:06 +0000, Richard Purdie wrote:
> On Tue, 2012-01-03 at 17:42 +0000, 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_IDLDIR = "${STAGING_DATADIR}/idl"
> 
> These are very old, I remember looking at them at various times but
> there was always something else to distract me. I'd be happy to take a
> patch removing them. If anything does break, there are better ways to
> fix it.

Okay, I'll send a patch for that presently.

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 palmtopdir = "${libdir}/opie"
export palmqtdir = "${palmtopdir}"

Paul, do you know if these variables are still necessary, whether they
all need to be exported, and/or whether they could go in some opie class
rather than bitbake.conf?

p.






More information about the Openembedded-core mailing list