From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] using of local dir
Date: Wed, 26 Mar 2008 22:41:48 +0100 [thread overview]
Message-ID: <87hcetyxgj.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <032301c88f86$de33de70$060514ac@atmel.com> (Ulf Samuelsson's message of "Wed\, 26 Mar 2008 21\:36\:02 +0100")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Hi,
>> It indeed seems quite broken. The $LOCAL variable isn't used
>> anywhere either.
Ulf> Check "project.mk"
Ahh. Why isn't the variable set there if it's only used in project.mk
anyway?
Bernhard> *shrug* I'd rip it out in a whim either way
>>
>> Well, the local/save/getconfig stuff does seem kinda overengineered -
>> Couldn't we just have a bunch of *_defconfig files under configs/
>> instead with a make %_defconfig target like the kernel has instead?
>>
Ulf> The purpose of this is to allow you to start with an existing
Ulf> defconfig, and the commands will collects the different
Ulf> configurations in one place. You can't replace this function
Ulf> with defconfigs, but you can use the result to create new
Ulf> defconfigs.
Ulf> At this time, not having access to the source tree, I can't see why LOCAL
Ulf> is defined *after* the include, so maybe this needs to be moved.
Ulf> Feel free to test.
No thanks - You made the mess, and you get to clean it up.
<grumpy-mode>
I really think we need to focus on getting the basic functionality of
buildroot stable and working so we can put out a release instead of
adding (what atleast looks like) half baked extensions.
</grumpy-mode>
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-03-26 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 17:59 [Buildroot] using of local dir Dittmann, Daniel
2008-03-26 18:09 ` Bernhard Fischer
2008-03-26 20:12 ` Peter Korsgaard
2008-03-26 20:36 ` Ulf Samuelsson
2008-03-26 21:41 ` Peter Korsgaard [this message]
2008-03-27 2:57 ` Hamish Moffatt
2008-03-27 5:14 ` Ulf Samuelsson
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=87hcetyxgj.fsf@macbook.be.48ers.dk \
--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 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.