From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: Machine specific sysroot issue
Date: Mon, 15 Aug 2011 15:42:16 +0100 [thread overview]
Message-ID: <201108151542.16948.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <B0416E2E-1F00-40F5-83F3-230D341239F5@dominion.thruhere.net>
On Monday 15 August 2011 15:30:53 Koen Kooi wrote:
> > Same way it gets installed, it looks for it in ${OPIEDIR}. It's just that
> > the second time around if the machine is not the same, ${OPIEDIR} is not
> > the same either.
>
> That sounds like an expanded version is getting stored somewhere where it
> shouldn't
How could that be the case? If it stayed the same I could understand it...
It's pretty straightforward; OPIEDIR is set to STAGING_DIR_HOST, but
STAGING_DIR_HOST is now ${STAGING_DIR}/${MACHINE}, thus if you change the
machine, STAGING_DIR_HOST also changes. In OE-dev (and Poky prior to machine-
specific sysroots) STAGING_DIR_HOST was ${STAGING_DIR}/${BASEPKG_HOST_SYS},
thus there was no problem.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-08-15 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 19:50 Machine specific sysroot issue Paul Eggleton
2011-08-14 22:05 ` Khem Raj
2011-08-15 14:15 ` Richard Purdie
2011-08-15 14:23 ` Paul Eggleton
2011-08-15 14:30 ` Koen Kooi
2011-08-15 14:42 ` Paul Eggleton [this message]
2011-08-15 14:58 ` Koen Kooi
2011-08-15 15:03 ` Phil Blundell
2011-08-15 15:49 ` Paul Eggleton
2011-08-15 15:51 ` Khem Raj
2011-08-15 15:52 ` Phil Blundell
2011-08-15 15:57 ` Richard Purdie
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=201108151542.16948.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox