All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Conroy <Chris.Conroy@hillcrestlabs.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] external-toolchain: Really accept toolchains built by meta-toolchain.bb
Date: Mon, 23 Nov 2009 10:26:48 -0500	[thread overview]
Message-ID: <1258990008.8426.29.camel@conroy-linux> (raw)
In-Reply-To: <1258901140-30575-1-git-send-email-bernhard.kaindl@gmx.net>

On Sun, 2009-11-22 at 15:45 +0100, Bernhard Kaindl wrote:
> external-toolchain-generic,
> external-toolchain:
> 
> * The current external-toolchain recipes which are documented to accept
>   toolchains built by meta-toolchain actually do not accept such because
>   they expect ${prefix}/package-status to exist which is provieded by
>   the poky toolchains but not the current OE meta-toolchain package.
> 
>   Fix this by also looking for ${prefix}/usr/lib/opkg/status, which is the
>   package-status file of the OE meta-toolchain package.
> 
> * Also change the error message which is shown when neither file is found
>   more explicit.

What about changing the meta-toolchain to generate the environment-setup
script? While it's not important to have the script for normal building
of packages, I've found it helpful to be able to do a quick compile of a
test program here or there. Though, I understand that it might be
dangerous since some folks might think the environment-setup creates an
an entire cross building platform for them when they really want to stay
inside OE....

--Chris



  reply	other threads:[~2009-11-23 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-22 14:45 [PATCH] external-toolchain: Really accept toolchains built by meta-toolchain.bb Bernhard Kaindl
2009-11-23 15:26 ` Chris Conroy [this message]
2009-11-23 17:19   ` Chris Simmonds
2009-11-23 18:31     ` Chris Conroy
2009-11-23 19:24       ` Chris Simmonds

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=1258990008.8426.29.camel@conroy-linux \
    --to=chris.conroy@hillcrestlabs.com \
    --cc=openembedded-devel@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.