From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Ideas for scripts, to save work, when building several boards
Date: Thu, 13 Aug 2009 14:10:24 +0200 [thread overview]
Message-ID: <4A8402B0.1000308@atmel.com> (raw)
In-Reply-To: <h60t34$5kl$1@ger.gmane.org>
Koen Kooi skrev:
> On 13-08-09 12:07, Ulf Samuelsson wrote:
>> Koen Kooi skrev:
>>> On 13-08-09 09:13, Ulf Samuelsson wrote:
>>>> Since I will need to test multiple boards,
>>>> I decided to write some scripts which I will
>>>> check in later today in origin/ulf/linux-2.6.30.2
>>>>
>>>> I generated a "MAKEALL" script which will
>>>> source a file "board_list.sh" with board build commands
>>>>
>>>> <SOF>
>>>> build_board sam9263dfc x11-gpe-image
>>>> build_board sam9g45ek opie-image
>>>> build_board sam9g10df x11-gpe-image
>>>> build_board sam9g20dfc console-image
>>>> build_board sam9260dfc console-image
>>>> build_board sam9261df x11-image
>>>> build_board sam9xedfc console-image
>>>> <EOF>
>>>
>>> You do know that you can do that with MACHINE=foo bitbake bar, right?
>>>
>>
>> Didn't try that.
>> I assume this means that the cross compiler is not rebuilt,
>
> Unless you poked at the gcc recipes, no, it won't get rebuilt.
>
>> Is the root fs assembled from ipks then?
>
> if you use rootfs_ipk.bbclass, yes.
>
> Note that the official angstrom buildguide has mentioned that for years:
> http://www.angstrom-distribution.org/building-angstrom
>
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
I believe that most at91 chips can use the same file system,
so it makes sense to do it this way anyway.
I assume that the at91sam9261df setup is used for the console-image.
There could be a few cases where this is ineffient or simply wrong.
> regards,
>
> Koen
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2009-08-13 12:26 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 [this message]
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
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=4A8402B0.1000308@atmel.com \
--to=ulf.samuelsson@atmel.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.