* [Buildroot] PATCH/RFC: Move all project specific files into the output directory
@ 2010-01-27 12:06 Will Wagner
2010-01-27 12:09 ` Lionel Landwerlin
0 siblings, 1 reply; 2+ messages in thread
From: Will Wagner @ 2010-01-27 12:06 UTC (permalink / raw)
To: buildroot
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
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.
Is anyone interested in getting this merged? All feedback welcome, let
me know if the patch needs more work.
Will
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 0011-Moved-config-files-into-output-directory.patch
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100127/3144b11a/attachment.diff>
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Buildroot] PATCH/RFC: Move all project specific files into the output directory
2010-01-27 12:06 [Buildroot] PATCH/RFC: Move all project specific files into the output directory Will Wagner
@ 2010-01-27 12:09 ` Lionel Landwerlin
0 siblings, 0 replies; 2+ messages in thread
From: Lionel Landwerlin @ 2010-01-27 12:09 UTC (permalink / raw)
To: buildroot
This was missing, great !
The kernel is able to put all generated files outside of its source tree, it
might be possible here too.
--
Lionel
On Wed, Jan 27, 2010 at 1:06 PM, Will Wagner <will_wagner@carallon.com>wrote:
> 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 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.
>
> Is anyone interested in getting this merged? All feedback welcome, let me
> know if the patch needs more work.
>
> Will
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100127/e4c8758d/attachment.htm>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-01-27 12:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-01-27 12:06 [Buildroot] PATCH/RFC: Move all project specific files into the output directory Will Wagner
2010-01-27 12:09 ` Lionel Landwerlin
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.