From: Chris Simmonds <chris@2net.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] external-toolchain: Really accept toolchains built by meta-toolchain.bb
Date: Mon, 23 Nov 2009 17:19:34 +0000 [thread overview]
Message-ID: <4B0AC426.3030505@2net.co.uk> (raw)
In-Reply-To: <1258990008.8426.29.camel@conroy-linux>
Chris Conroy wrote:
> 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
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.
next prev parent reply other threads:[~2009-11-23 17:34 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 [this message]
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=4B0AC426.3030505@2net.co.uk \
--to=chris@2net.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox