From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Where does 'BOARD_NAME' Makefile.in variable come from?
Date: Fri, 16 Apr 2010 16:18:18 +0000 (UTC) [thread overview]
Message-ID: <hqa2ka$uek$1@dough.gmane.org> (raw)
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
next reply other threads:[~2010-04-16 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 16:18 Grant Edwards [this message]
2010-04-16 16:29 ` [Buildroot] Where does 'BOARD_NAME' Makefile.in variable come from? Andrew Porritt
2010-04-16 16:49 ` Grant Edwards
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='hqa2ka$uek$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
/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.