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 13:31:48 -0500 [thread overview]
Message-ID: <1259001108.19077.4.camel@conroy-linux> (raw)
In-Reply-To: <4B0AC426.3030505@2net.co.uk>
On Mon, 2009-11-23 at 17:19 +0000, Chris Simmonds wrote:
> meta-toolchain does generate environment-setup and so far as I am aware
> it works fine as a stand-alone toolchain. Is there some reason why I
> should not be using it as such?
>
> Chris S.
It's fine as just a standalone toolchain. It's just not a "Build
Platform." Meaning, you can't just source it and get all the other
things that OE gives you. This is perhaps too obvious to even warrant
mentioning.
I misinterpreted the original patch since I was comparing against my
local tree, where we've modified to check for environment-setup rather
than package-status (simply as a sanity check for the setting of
${prefix}, so you can safely disregard my previous posting.
--Chris
next prev parent reply other threads:[~2009-11-23 18:33 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
2009-11-23 17:19 ` Chris Simmonds
2009-11-23 18:31 ` Chris Conroy [this message]
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=1259001108.19077.4.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.