From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1213] New: Move .config into output directory
Date: Mon, 1 Mar 2010 19:08:43 +0000 (UTC) [thread overview]
Message-ID: <bug-1213-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=1213
Summary: Move .config into output directory
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Windows
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: will_wagner at carallon.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=1177)
--> (https://bugs.busybox.net/attachment.cgi?id=1177)
Move .config into output directory
Currently buildroot places most files generated by the build in the output
directory (which can be overriden with O=). However a number of files remain
within the buildroot tree.
These are:
.auto.deps (incidentally this no longer seems to be used)
.config
.config.cmd
.config.old
package/config/buildroot-config (which then gets copied into output/build)
This is a problem if you want to use the same buildroot directory to
simultaneously build two different targets to locations elsewhere in the
filesystem with O=
The patch modifies config and the top level Makefile so that all files reside
in the output folder. Feedback welcome. Could go further and tidy some things
up as well but have not done so. In particular we generate .auto.deps but never
seem to use it. Also have not updated
package/config/kconfig-to-buildroot2.patch as the previous patch was old and
the instructions on how to generate it were incorrect.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-03-01 19:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 19:08 bugzilla at busybox.net [this message]
2010-03-17 15:23 ` [Buildroot] [Bug 1213] Move .config into output directory bugzilla at busybox.net
2010-03-19 8:44 ` bugzilla at busybox.net
2010-03-19 12:16 ` Bjørn Forsman
2010-04-01 16:04 ` bugzilla at busybox.net
2010-04-01 16:06 ` bugzilla at busybox.net
2010-04-01 16:10 ` bugzilla at busybox.net
2010-04-09 10:42 ` bugzilla at busybox.net
2010-04-09 14:43 ` bugzilla at busybox.net
2010-04-09 16:46 ` bugzilla at busybox.net
2010-04-13 16:13 ` bugzilla at busybox.net
2010-04-14 10:56 ` bugzilla at busybox.net
2010-04-14 11:23 ` bugzilla at busybox.net
2010-06-09 18:25 ` bugzilla at busybox.net
2010-06-09 19:12 ` bugzilla at busybox.net
2010-06-21 21:08 ` bugzilla at busybox.net
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=bug-1213-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.