Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Where does 'BOARD_NAME' Makefile.in variable come from?
@ 2010-04-16 16:18 Grant Edwards
  2010-04-16 16:29 ` Andrew Porritt
  0 siblings, 1 reply; 3+ messages in thread
From: Grant Edwards @ 2010-04-16 16:18 UTC (permalink / raw)
  To: buildroot

I'm looking at the default config files and Makefile.in files for the
Atmel boards, and they all reference a variable named "BOARD_NAME".
For example from target/device/Atmel/at91sam9261ek/Makefile.in:

ifeq ($(strip $(BOARD_NAME)),at91sam9261ek)
LINUX_BOARD_NAME:=at91sam9261ek
...

And from at91sam9263ek_defconfig

BR2_TARGET_AT91BOOTSTRAP_BOARD="$(BOARD_NAME)"

But, I can't figure out where BOARD_NAME comes from or how it differs
from BR2_BOARD_NAME.  Can somebody point me towards a clue?

-- 
Grant Edwards               grant.b.edwards        Yow! My LESLIE GORE record
                                  at               is BROKEN ...
                              gmail.com            

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Buildroot] Where does 'BOARD_NAME' Makefile.in variable come from?
  2010-04-16 16:18 [Buildroot] Where does 'BOARD_NAME' Makefile.in variable come from? Grant Edwards
@ 2010-04-16 16:29 ` Andrew Porritt
  2010-04-16 16:49   ` Grant Edwards
  0 siblings, 1 reply; 3+ messages in thread
From: Andrew Porritt @ 2010-04-16 16:29 UTC (permalink / raw)
  To: buildroot

I think you pass it in on the command line. E.g.:

make BOARD_NAME=at91sam9261ek

On 16/04/2010 17:18, Grant Edwards wrote:
> I'm looking at the default config files and Makefile.in files for the
> Atmel boards, and they all reference a variable named "BOARD_NAME".
> For example from target/device/Atmel/at91sam9261ek/Makefile.in:
>
> ifeq ($(strip $(BOARD_NAME)),at91sam9261ek)
> LINUX_BOARD_NAME:=at91sam9261ek
> ...
>
> And from at91sam9263ek_defconfig
>
> BR2_TARGET_AT91BOOTSTRAP_BOARD="$(BOARD_NAME)"
>
> But, I can't figure out where BOARD_NAME comes from or how it differs
> from BR2_BOARD_NAME.  Can somebody point me towards a clue?
>
>    
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100416/bf36865f/attachment.htm>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Buildroot] Where does 'BOARD_NAME' Makefile.in variable come from?
  2010-04-16 16:29 ` Andrew Porritt
@ 2010-04-16 16:49   ` Grant Edwards
  0 siblings, 0 replies; 3+ messages in thread
From: Grant Edwards @ 2010-04-16 16:49 UTC (permalink / raw)
  To: buildroot

On 2010-04-16, Andrew Porritt <aporritt@gogo-robot.com> wrote:
> I think you pass it in on the command line. E.g.:
>
> make BOARD_NAME=at91sam9261ek

I've never done that, and I can't find it mentioned in any of the docs
(either from buildroot or from Atmel).

I think it might be something Atmel-specific...

-- 
Grant Edwards               grant.b.edwards        Yow! Did I say I was
                                  at               a sardine?  Or a bus???
                              gmail.com            

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-04-16 16:49 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-16 16:18 [Buildroot] Where does 'BOARD_NAME' Makefile.in variable come from? Grant Edwards
2010-04-16 16:29 ` Andrew Porritt
2010-04-16 16:49   ` Grant Edwards

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox