[Buildroot] Overriding DL_DIR in the environment
mcrane03 at harris.com
Mon Aug 20 14:15:17 UTC 2007
So far everyone has explained that a common location can be *achieved*
but that does not mean that it is superior to doing it with the help of
I am convinced that it is better to do it using the environment.
My question is really is if anyone can show any drawback in having this
functionality in buildroot.
(Even if it is there, you don't have to use it)
How is the dl dir different from many other settings that could aslo be
left in the environment?
If you have your setting in the environment can it not be picked up as
the default value for that config text entry? I think too that
quantifying the keystrokes is a superficial measure of the utility of
using environment variables, it is complexity that should be reduced and
maintainability that ought to be considered.
From: Ulf Samuelsson [mailto:ulf at atmel.com]
Sent: Friday, August 17, 2007 4:43 PM
To: Crane, Matthew; buildroot at uclibc.org
Subject: Re: [Buildroot] Overriding DL_DIR in the environment
> -----Original Message-----
> From: buildroot-bounces at uclibc.org
[mailto:buildroot-bounces at uclibc.org]
> On Behalf Of Cristian Ionescu-Idbohrn
> Sent: Friday, August 17, 2007 1:59 PM
> To: buildroot at uclibc.org
> Subject: Re: [Buildroot] Overriding DL_DIR in the environment
> On Fri, 17 Aug 2007, 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".
> Wouldn't a symlink (that's what I use) sort that out?
More information about the buildroot