From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Makefile: generate a Makefile wrapper in $(O)
Date: Sat, 16 Oct 2010 15:24:24 +0200 [thread overview]
Message-ID: <87d3rae0dz.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1287232474.3927.190.camel@coalu.atr> (Lionel Landwerlin's message of "Sat, 16 Oct 2010 14:34:34 +0200")
>>>>> "Lionel" == Lionel Landwerlin <llandwerlin@gmail.com> writes:
Lionel> Yann,
Lionel> I'm having a problem with the last buildroot on git. I'm not sure this
Lionel> is related to your patches.
Lionel> In a clean buildroot repository (no output directory already present),
Lionel> if you do :
Lionel> $ make menuconfig
Lionel> The .config files are created in the root of the buildroot tree instead
Lionel> of in the output/ directory.
That's how it has always been. It would be conceptually cleaner to put
it in output/, but we're keeping it in the toplevel dir for legacy
reasons (and because other projects using kconfig do that as well).
Lionel> I might be wrong, but I was used to the second behavior.
Lionel> Could you check this isn't a problem introduced by your patches ?
Lionel> Otherwise I will try figure this out later.
No, we have never put it in output by default. If you want that, simply
run make O=output menuconfig.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-10-16 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 8:56 [Buildroot] [PATCH] Makefile: generate a Makefile wrapper in $(O) Yann E. MORIN
2010-09-26 21:48 ` Peter Korsgaard
2010-09-28 16:36 ` Yann E. MORIN
2010-10-16 12:34 ` Lionel Landwerlin
2010-10-16 13:24 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-21 22:25 Yann E. MORIN
2010-09-23 21:04 ` Peter Korsgaard
2010-09-23 21:35 ` Yann E. MORIN
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=87d3rae0dz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox