From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Ideas for scripts, to save work, when building several boards
Date: Thu, 13 Aug 2009 15:55:02 +0200 [thread overview]
Message-ID: <h615vm$15q$1@ger.gmane.org> (raw)
In-Reply-To: <200908131456.10488.holger+oe@freyther.de>
On 13-08-09 14:56, Holger Hans Peter Freyther wrote:
> On Thursday 13 August 2009 14:10:24 Ulf Samuelsson wrote:
>
>> Thanks for helping out, but it does not work as expected.
>>
>> I first create a local.conf for the at91sam9261df
>> and bitbake x11-image.
>> Then I do "MACHINE=at91sam9g20dfc bitbake console-image".
>> A console-image is built,but for the at91sam9261df,
>> which is stored in "tmp/deploy/glibc/images/at91sam9261df"
>>
>> The bitbake does not generate u-boot/kernel or at91bootstrap
>> for the at91sam9260dfc
>
> Stupid question. The task that should pull in u-boot/kernel or at91bootstrap
> is not machine specific?
Hey, you spoilt the punchline to my teach-a-man-to-fish routine :)
next prev parent reply other threads:[~2009-08-13 14:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 7:13 Ideas for scripts, to save work, when building several boards Ulf Samuelsson
2009-08-13 8:38 ` Koen Kooi
2009-08-13 10:07 ` Ulf Samuelsson
2009-08-13 11:23 ` Koen Kooi
2009-08-13 12:10 ` Ulf Samuelsson
2009-08-13 12:44 ` Koen Kooi
2009-08-13 15:23 ` Ulf Samuelsson
2009-08-13 16:30 ` Koen Kooi
2009-08-13 20:36 ` Ulf Samuelsson
2009-08-13 21:18 ` Koen Kooi
2009-08-14 7:44 ` Ulf Samuelsson
2009-08-20 19:41 ` Marcin Juszkiewicz
2009-08-22 7:50 ` Ulf Samuelsson
2009-08-24 16:39 ` Otavio Salvador
2009-08-13 12:56 ` Holger Hans Peter Freyther
2009-08-13 13:55 ` Koen Kooi [this message]
2009-08-13 14:19 ` Holger Hans Peter Freyther
2009-08-13 12:18 ` Ulf Samuelsson
2009-08-13 12:46 ` Koen Kooi
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='h615vm$15q$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.