From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] New kernel source mode [Proposal]
Date: Tue, 15 Jan 2013 08:51:16 +0100 [thread overview]
Message-ID: <50F50A74.8000501@relinux.de> (raw)
In-Reply-To: <EE5E77B503DE9A478B63A89AAD2585EDB66A2F@vpane.excalyptech.com>
Am 15.01.2013 02:12, schrieb Przemyslaw Wrzos:
>
> Hi,
>
>
>
> I'd like to get some feedback on a feature I'd like to contribute to
> the buildroot project. I'm not quite sure what the process is so I
> thought I'd start on the mailing list.
>
>
>
>
>
> PROPOSAL: Allow a directory (containing the source tree) to be used
> as the source for the kernel build. The source isn't copied to the
> output directory but instead the kernel's outputmakfile wrapper
> facility is used.
>
>
>
Hello,
do you mean the kernel's out of tree build feature?
> RATIONALE: In my project, changes to the kernel are frequent enough
> that it is ideal to be able to update the kernel source tree and then
> build directly from it.
>
Isn't this almost the same as can be achieved using the "Source
Override" feature?
But the advantages of your proposal would be saving some time on each
build and some hard disk space. Especially when using huge kernel git
archives.
>
>
>
> IMPLEMENTATION: In addition to providing a new source for the linux
> build process itself, some package makefiles will need to be updated
> as they currently don't differentiate between the kernel source tree
> and build tree.
>
>
>
>
>
> I have this working already though I still need to update some of the
> packages as mentioned above. I wanted to ask if there would be any
> interest in rolling this into the buildroot project upstream.
>
If you send your patch set I'll give it a try, but I cannot judge the
impact of buildroot's overall structure.
Kind regards
Stephan
>
>
>
> Thanks for your feedback.
>
>
>
> _______________________________________________
> 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/20130115/2fd7397d/attachment.html>
next prev parent reply other threads:[~2013-01-15 7:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 1:12 [Buildroot] New kernel source mode [Proposal] Przemyslaw Wrzos
2013-01-15 7:51 ` Stephan Hoffmann [this message]
2013-01-17 6:25 ` Przemyslaw Wrzos
2013-01-17 6:27 ` Przemyslaw Wrzos
2013-01-18 1:10 ` Przemyslaw Wrzos
2013-01-18 8:14 ` Stephan Hoffmann
2013-01-21 0:23 ` Przemyslaw Wrzos
2013-01-15 7:55 ` Thomas Petazzoni
2013-01-15 8:18 ` Jeremy Rosen
2013-01-15 8:22 ` Thomas Petazzoni
2013-01-15 9:13 ` Jeremy Rosen
2013-01-15 9:24 ` Thomas Petazzoni
2013-01-15 9:27 ` Jeremy Rosen
2013-01-19 16:13 ` Arnout Vandecappelle
2013-01-17 6:59 ` Przemyslaw Wrzos
2013-01-15 18:23 ` Steve Calfee
2013-01-15 20:40 ` Peter Korsgaard
2013-01-19 16:16 ` Arnout Vandecappelle
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=50F50A74.8000501@relinux.de \
--to=sho@relinux.de \
--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