All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] buildroot:linux: Add options to checkout Linux kernel source from SVN or GIT repository.
Date: Fri, 17 Dec 2010 11:40:23 +0100	[thread overview]
Message-ID: <20101217114023.6459c16e@surf> (raw)
In-Reply-To: <1292492992-15797-2-git-send-email-sonic.adi@gmail.com>

Hello,

On Thu, 16 Dec 2010 17:49:52 +0800
Sonic Zhang <sonic.adi@gmail.com> wrote:

> Current buildroot Config.in and linux.mk don't support kernel source in SVN
> or GIT repository. A pre-checkouted local SVN or GIT kernel tree set in
> KERNEL_CUSTOM_TREE is the only option.

The KERNEL_CUSTOM_TREE option is not in mainline Buildroot. And as per
my answer to the previous patch, I'd very much prefer a more generic
solution than a solution specific to the Linux kernel build process.

> Because the local path can be anywhere, no buildroot default config file can be defined in sub folder
> target/device/company/boards to run quick building. It is inconvient to run
> regression testing. Since buildroot has already support SVN and GIT repository
> for application packages, it is reasonable to have it for linux kernel as well.

I have a similar comment here: I agree that we must have GIT and SVN
support for the Linux build process, but we should also have it for all
the bootloaders (see the recent patch to introduce X-Loader).
Therefore, instead of solving it in a Linux-specific way, I'd prefer if
we could have a generic infrastructure (in the spirit of the package
infrastructure) that would satisfy the need of bootloaders and Linux
kernel in terms of build process.

Yes, it's a lot more work than just making the change on the Linux
kernel build process only, but on the long term, it's much more
interesting.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-12-17 10:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16  9:49 [Buildroot] [PATCH v2] buildroot:download: Add option to download SVN or GIT repository with version control information Sonic Zhang
2010-12-16  9:49 ` [Buildroot] [PATCH v2] buildroot:linux: Add options to checkout Linux kernel source from SVN or GIT repository Sonic Zhang
2010-12-17 10:40   ` Thomas Petazzoni [this message]
2010-12-16 14:19 ` [Buildroot] [PATCH v2] buildroot:download: Add option to download SVN or GIT repository with version control information Quotient Remainder
2010-12-17  2:44   ` Sonic Zhang
2010-12-16 21:22 ` Lionel Landwerlin
2010-12-17  2:52   ` Sonic Zhang
2010-12-17 10:34 ` Thomas Petazzoni
2010-12-17 13:11   ` Quotient Remainder
2010-12-20 14:05     ` Thomas Petazzoni
2010-12-20 16:04       ` Quotient Remainder
2010-12-20 16:08         ` Thomas Petazzoni
2010-12-20 16:37           ` Quotient Remainder
2010-12-20 16:47             ` Thomas Petazzoni
2010-12-20  9:11   ` Sonic Zhang
2010-12-20 11:37     ` Daniel Nyström

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=20101217114023.6459c16e@surf \
    --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 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.