From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6] relocatable SDK
Date: Mon, 30 Jul 2012 13:30:40 +0100 [thread overview]
Message-ID: <1343651440.786.1.camel@ted> (raw)
In-Reply-To: <50164ADE.9030603@intel.com>
On Mon, 2012-07-30 at 11:50 +0300, Laurentiu Palcu wrote:
> Hi Philip,
>
> >>> The user will then execute the .sh script and give it the target
> >>> directory for SDK installation (default is /opt/poky). The installer
> >
> > For oe-core the default should be something like /opt/oe-core, not
> > /opt/some-distro.
> This a good observation.
>
> SDKPATH = "/opt/${DISTRO}/${SDK_VERSION}"
>
> I will change the installer/setup scripts so that the default SDK
> installation directory takes into account the DISTRO variable.
SDKPATH is the right variable to use for this. The above is from
poky.conf and is a valid distro configuration option. The OE-Core
default doesn't use distro and installs into /usr/local/oecore/
Cheers,
Richard
prev parent reply other threads:[~2012-07-30 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 11:21 [PATCH 0/6] relocatable SDK Laurentiu Palcu
2012-07-27 11:21 ` [PATCH 1/6] eglibc: relocatable SDK changes Laurentiu Palcu
2012-07-27 11:21 ` [PATCH 2/6] binutils: relocatable SDK: change PT_INTERP section size Laurentiu Palcu
2012-07-27 11:21 ` [PATCH 3/6] scripts: add script for relocating the SDK Laurentiu Palcu
2012-07-27 11:21 ` [PATCH 4/6] populate_sdk_base.bbclass: create self-extracting archive Laurentiu Palcu
2012-07-27 11:21 ` [PATCH 5/6] relocatable.bbclass: split it up, to reuse code Laurentiu Palcu
2012-07-27 11:21 ` [PATCH 6/6] package.bbclass: change RPATHs for nativesdk packages Laurentiu Palcu
2012-07-27 18:05 ` [PATCH 0/6] relocatable SDK Saul Wold
2012-07-29 12:06 ` Philip Balister
2012-07-30 8:50 ` Laurentiu Palcu
2012-07-30 12:30 ` Richard Purdie [this message]
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=1343651440.786.1.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 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.