From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Overriding DL_DIR in the environment
Date: Mon, 20 Aug 2007 16:34:02 +0200 [thread overview]
Message-ID: <20070820143402.GA23522@aon.at> (raw)
In-Reply-To: <1187370334.31026.4.camel@elrond.sweden.atmel.com>
On Fri, Aug 17, 2007 at 07:05:34PM +0200, Ulf Samuelsson wrote:
>I keep a central download location for all tarballs,
>and find it a pain to always have to edit the DL_DIR
>variable during "make menuconfig".
>
>It would be nice to be able to override the ".config"
>value of DL_DIR in the shell environment.
>
>Here is a simple patch which will,
>if you define
>
>$ export BUILDROOT_DL_DIR /usr/local/install/downloads
>
>in your ".bashrc", override the DL_DIR in the ".config".
>
>
>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>Index: Makefile
>===================================================================
>--- Makefile (revision 19542)
>+++ Makefile (arbetskopia)
>@@ -37,6 +37,9 @@
> ifeq ($(filter $(noconfig_targets),$(MAKECMDGOALS)),)
> -include $(TOPDIR).config
> endif
>+ifneq ($(BUILDROOT_DL_DIR),)
This is whitespace-damaged (once again..)
If you add this to be noted via dependencies.sh then it's fine for me
provided that you fix that whitespace damage above.
That said, i usually symlink the DL_DIR to my usual repo of tarballs,
fwiw.
>+BR2_DL_DIR:=$(BUILDROOT_DL_DIR)
>+endif
>
> # To put more focus on warnings, be less verbose as default
> # Use 'make V=1' to see the full commands
>--------------------------------------------------------------------
>
>
>
>Comments?
prev parent reply other threads:[~2007-08-20 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 17:05 [Buildroot] Overriding DL_DIR in the environment Ulf Samuelsson
2007-08-17 17:59 ` Cristian Ionescu-Idbohrn
2007-08-17 19:05 ` Crane, Matthew
2007-08-17 20:42 ` Ulf Samuelsson
2007-08-20 14:15 ` Crane, Matthew
2007-08-20 14:34 ` Bernhard Fischer [this message]
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=20070820143402.GA23522@aon.at \
--to=rep.dot.nop@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox