Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/ARM
Date: Sun,  6 Apr 2008 01:08:07 -0700 (PDT)	[thread overview]
Message-ID: <20080406080807.D52B23C3A2@busybox.net> (raw)

Author: jacmet
Date: 2008-04-06 01:08:07 -0700 (Sun, 06 Apr 2008)
New Revision: 21647

Log:
target/device/ARM: Don't override Config settings

Don't override board name/path with hardcoded values in Makefile.


Modified:
   trunk/buildroot/target/device/ARM/Makefile.in


Changeset:
Modified: trunk/buildroot/target/device/ARM/Makefile.in
===================================================================
--- trunk/buildroot/target/device/ARM/Makefile.in	2008-04-06 07:17:02 UTC (rev 21646)
+++ trunk/buildroot/target/device/ARM/Makefile.in	2008-04-06 08:08:07 UTC (rev 21647)
@@ -1,8 +1,7 @@
 ifeq ($(BR2_TARGET_ARM),y)
 
-BOARD_NAME=arm
-BR2_BOARD_PATH:=target/device/ARM
-BOARD_PATH:=target/device/ARM
+BOARD_NAME:=$(strip  $(subst ",, $(BR2_BOARD_NAME)))
+BOARD_PATH:=$(strip  $(subst ",, $(BR2_BOARD_PATH)))
 
 # These are set by Config.in
 DOWNLOAD_LINUX26_VERSION:=$(strip  $(subst ",, $(BR2_DOWNLOAD_LINUX26_VERSION)))

             reply	other threads:[~2008-04-06  8:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06  8:08 jacmet at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-06  8:19 [Buildroot] svn commit: trunk/buildroot/target/device/ARM jacmet at uclibc.org
2008-04-05 16:59 jacmet at uclibc.org
2008-04-05 16:11 jacmet at uclibc.org
2008-03-29 20:36 ulf at uclibc.org
2007-09-27 22:04 [Buildroot] svn commit: trunk/buildroot/target/device/Arm aldot at uclibc.org
2007-09-27 21:23 aldot at uclibc.org

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=20080406080807.D52B23C3A2@busybox.net \
    --to=jacmet@uclibc.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox