From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Cc: bitbake-dev@lists.berlios.de
Subject: Re: Bitbake release
Date: Sat, 06 Dec 2008 19:23:07 +0100 [thread overview]
Message-ID: <ghefuc$699$1@ger.gmane.org> (raw)
In-Reply-To: <20081206175006.GI16628@smtp.west.cox.net>
On 06-12-08 18:50, Tom Rini wrote:
> On Sat, Dec 06, 2008 at 04:32:52PM +0100, Koen Kooi wrote:
>> On 06-12-08 15:39, Richard Purdie wrote:
>>> Hi,
>>>
>>> As people have probably noticed I just synced up a number of useful
>>> changes from Poky into bitbake and brought things pretty much back into
>>> sync.
>>>
>>> The current plan is to let this stabilise for 1 week and the providing
>>> no major bugs were introduced, make a new release (finally!).
>> Not a bug, but something for people to note:
>>
>> http://projects.linuxtogo.org/pipermail/openembedded-devel/2008-October/006289.html
>
>
> As I asked at the time, what's this doing? Do all distros need to do
> this? What's Angstrom doing on the metadata side to make use of this?
> Thanks!
The angstrom buildscripts
(http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/contrib/angstrom)
pass MACHINE and ANGSTROM_MODE via the shell enviroment to avoid
spurious reparsing. Since bitbake clean the environment the vars don't
get into bitbake.
regards,
Koen
next prev parent reply other threads:[~2008-12-06 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 14:39 Bitbake release Richard Purdie
2008-12-06 15:32 ` Koen Kooi
2008-12-06 17:50 ` Tom Rini
2008-12-06 18:23 ` Koen Kooi [this message]
2008-12-06 22:13 ` Paul Sokolovsky
2008-12-06 22:56 ` Richard Purdie
2008-12-08 10:37 ` Koen Kooi
2008-12-16 13:19 ` Holger Freyther
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='ghefuc$699$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=bitbake-dev@lists.berlios.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.