From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Extending buildroot functionality for creating board support packages (BSP) out of buildroot tree
Date: Sat, 13 Apr 2013 16:25:05 +0200 [thread overview]
Message-ID: <20130413162505.635dec45@skate> (raw)
In-Reply-To: <trinity-fb9dabe2-fdca-4333-b79a-0d5257710847-1365761929883@3capp-gmx-bs44>
Hello Andreas,
On Fri, 12 Apr 2013 12:18:49 +0200 (CEST), universeII at gmx.de wrote:
> If I understand you correctly this means that I have to hold a
> complete copy of the kernel tree where I do the modifications? The
> requirement for me is that I have to store only the modified and new
> files in a different directory tree (under version control). So rsync
> does not work for me and I have to write a small script which is
> invoked by buildroot and copies my local files to the right
> directories in the kernel tree.
While we certainly aim at supporting a custom external tree for the
Linux kernel sources to help using Buildroot during kernel development,
we will certainly never support your use case of a partial kernel tree
that contains only the modified and new files. This is just a very
uncommon (and in my opinion completely wrong) way of handling source
code changes. You should instead be using a git tree to do your kernel
developments, and point LINUX_OVERRIDE_SRCDIR to it.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-04-13 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 9:51 [Buildroot] Extending buildroot functionality for creating board support packages (BSP) out of buildroot tree universe II
2013-04-12 9:58 ` Jeremy Rosen
2013-04-12 10:18 ` universeII at gmx.de
2013-04-13 14:25 ` Thomas Petazzoni [this message]
2013-04-14 19:42 ` universe II
[not found] <trinity-2fc0f02e-0868-421f-b7b4-637396c65e9e-1365761778735@3capp-gmx-bs44>
2013-04-12 10:39 ` Jeremy Rosen
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=20130413162505.635dec45@skate \
--to=thomas.petazzoni@free-electrons.com \
--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