Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] New kernel source mode [Proposal]
Date: Tue, 15 Jan 2013 21:40:53 +0100	[thread overview]
Message-ID: <877gnemb6y.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAJJ6jxsbtr92TvkAfhz5m_Jxxp1DTA7_cmtnY5NKYMkJFYgHoQ@mail.gmail.com> (Steve Calfee's message of "Tue, 15 Jan 2013 10:23:36 -0800")

>>>>> "Steve" == Steve Calfee <stevecalfee@gmail.com> writes:

Hi,

 Steve> Hi, I am not opposed to a simple integration of kernel development
 Steve> into buildroot.

 Steve> However, the last time I did kernel hacking a few years ago with
 Steve> buildroot, we just did not build the kernel with BR. The greatly
 Steve> speeds up a BR build after a clean (If you also use an external
 Steve> toolchain).

 Steve> We had the kernel tree in an external git tree where we did standard
 Steve> cross builds using the same compilers used by the BR. A simple script
 Steve> to copy uImage and the modules to the nfs filesystem where BR was
 Steve> extracted made a testable system.

I work somewhat similar. I build the kernel by hand while I'm developing
on it (working on a driver or whatever), and the same for any custom
applications, and only use buildroot as an integration tool once the
individual components are more-or-less stable to ensure everything is
under version control and can be reproduced.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-01-15 20:40 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
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 [this message]
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=877gnemb6y.fsf@dell.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