From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] how BR download the linux kernel now
Date: Wed, 13 Jul 2011 16:14:51 +0200 [thread overview]
Message-ID: <20110713161451.791f42ea@skate> (raw)
In-Reply-To: <CAAa76NTwjrB-6jbenSbGDpN0evxnV-TVx36DvdNcvWnVQEfr4w@mail.gmail.com>
Le Wed, 13 Jul 2011 09:31:10 -0400,
raymond zhao <raymond.zhao.ml@gmail.com> a ?crit :
> That's great. I will definitely check it. If we solved this problem. I
> believe BR will be #1 choice for most embedded linux projects.
Thanks. I indeed think that this feature would be a really nice
addition to Buildroot. I miss it in many of the projects for which I
use Buildroot.
For the moment, my workaround is to not use Buildroot to build the part
of the system I'm actively working on. When I'm doing kernel
development, I build the kernel outside of Buildroot. When I develop an
application, I build the application outside of Buildroot. Buildroot is
here to build all the rest, and to provide a reproducible mechanism to
build the final system image.
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:[~2011-07-13 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 13:31 [Buildroot] how BR download the linux kernel now raymond zhao
2011-07-13 14:14 ` Thomas Petazzoni [this message]
2011-08-23 20:30 ` raymond zhao
2011-09-01 7:12 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2011-07-12 20:26 raymond zhao
2011-07-12 20:59 ` Yann E. MORIN
2011-07-12 22:03 ` raymond zhao
2011-07-13 7:46 ` Thomas Petazzoni
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=20110713161451.791f42ea@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