From: ulf at uclibc.org <ulf@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: docs
Date: Sun, 19 Aug 2007 16:32:34 -0700 (PDT) [thread overview]
Message-ID: <20070819233234.8D69DA467E@busybox.net> (raw)
Author: ulf
Date: 2007-08-19 16:32:33 -0700 (Sun, 19 Aug 2007)
New Revision: 19584
Log:
Add support for BUILDROOT_DL_DIR environment variable, overriding DL_DIR
Modified:
trunk/buildroot/Makefile
trunk/buildroot/docs/buildroot.html
Changeset:
Modified: trunk/buildroot/Makefile
===================================================================
--- trunk/buildroot/Makefile 2007-08-19 23:16:47 UTC (rev 19583)
+++ trunk/buildroot/Makefile 2007-08-19 23:32:33 UTC (rev 19584)
@@ -37,6 +37,9 @@
ifeq ($(filter $(noconfig_targets),$(MAKECMDGOALS)),)
-include $(TOPDIR).config
endif
+ifneq ($(BUILDROOT_DL_DIR),)
+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
Modified: trunk/buildroot/docs/buildroot.html
===================================================================
--- trunk/buildroot/docs/buildroot.html 2007-08-19 23:16:47 UTC (rev 19583)
+++ trunk/buildroot/docs/buildroot.html 2007-08-19 23:32:33 UTC (rev 19584)
@@ -779,6 +779,28 @@
toolchain and the target filesystem with exactly the same
versions. </p>
+ <p>If you maintain several buildroot trees, it might be better to have
+ a shared download location. This can be accessed by creating a symbolic link
+ from the <code>dl</code> directory to the shared download location. </p>
+
+ <p>I.E:</p>
+
+<pre>
+ln -s <shared download location> dl
+</pre>
+
+ <p>Another way of accessing a shared download location is to
+ create the <code>BUILDROOT_DL_DIR</code> environment variable.
+ If this is set, then the value of DL_DIR in the project is
+ overridden. The following line should be added to
+ <code>"~/.bashrc"</code>. <p>
+
+<pre>
+export BUILDROOT_DL_DIR <shared download location>
+</pre>
+
+
+
<h2><a name="add_software" id="add_software"></a>Extending Buildroot with
more software</h2>
reply other threads:[~2007-08-19 23:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070819233234.8D69DA467E@busybox.net \
--to=ulf@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