All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: weird exports in bitbake.conf
Date: Wed, 04 Jan 2012 12:24:21 +0000	[thread overview]
Message-ID: <1325679862.28005.44.camel@phil-desktop> (raw)
In-Reply-To: <1325678787.3555.134.camel@ted>

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.





  reply	other threads:[~2012-01-04 12:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 17:42 weird exports in bitbake.conf Phil Blundell
2012-01-04 12:06 ` Richard Purdie
2012-01-04 12:24   ` Phil Blundell [this message]
2012-01-04 13:49     ` Paul Eggleton
2012-01-04 15:06       ` Phil Blundell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1325679862.28005.44.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.