weird exports in bitbake.conf

weird exports in bitbake.conf

[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.

Re: weird exports in bitbake.conf

[Richard Purdie]

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.

Cheers,

Richard

Re: weird exports in bitbake.conf

[Phil Blundell]

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.

Re: weird exports in bitbake.conf

[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 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?

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 inheriting 
palmtop and will therefore break if these are removed. I want to tidy these up 
but can you give me until next week to do that?

Thanks,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: weird exports in bitbake.conf

[Phil Blundell]

On Wed, 2012-01-04 at 13:49 +0000, 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 inheriting 
> palmtop and will therefore break if these are removed. I want to tidy these up 
> but can you give me until next week to do that?

That would be great.  Thanks.

p.