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

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



  reply	other threads:[~2012-01-04 13:56 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
2012-01-04 13:49     ` Paul Eggleton [this message]
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=1794876.VcZe9uqeJk@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philb@gnu.org \
    /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.