All of lore.kernel.org
 help / color / mirror / Atom feed
From: raymond zhao <raymond.zhao.ml@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] how BR download the linux kernel now
Date: Tue, 12 Jul 2011 18:03:27 -0400	[thread overview]
Message-ID: <CAAa76NSqWgSvUZEgtpCGvk-Ly69P9wdfSoWz1q2XC=-y7EtKFg@mail.gmail.com> (raw)
In-Reply-To: <201107122259.14014.yann.morin.1998@anciens.enib.fr>

On Tue, Jul 12, 2011 at 4:59 PM, Yann E. MORIN <
yann.morin.1998@anciens.enib.fr> wrote:

> **
>
> Raymond, All,
>
> On Tuesday 12 July 2011 22:26:49 raymond zhao wrote:
>
> > I checked out the latest version of the buildroot, and noticed that
>
> > the linux.mk was changed a lot. Thomas checked in a version with log
>
> > message "linux: convert to the GENTARGETS infrastructure". And, from
>
> > there, I am confused. How the BR download the linux kernel now? I
>
> > mean, before this version, there are download, extraction and patch.
>
> > But they are removed and there is only LINUX_DOWNLOAD_PATCHES in the
>
> > new version. Where is the script for BR to download the kernel source
>
> > code now?
>
> In a word, it's automagic, now! :-)
>
> In a hundred words, look at linux/linux.mk:
>
> - on line 9-28, we set the two variables LINUX_SITE and LINUX_TARBALL
>
> depending on the user's options
>
> - on line 180, we call GENTARGETS that generates all the reuired rules
>
> - the variable LINUX_SITE tells where the kernel is to be get from
>
> - the variable LINUX_TARBALL tells the tarball's file name
>
> - the function GENTARGETS instantiates download+extract+build+install rules
>
> for the specified package
>
> GENTARGETS is defined in package/Makefile.package.in
>
> It's the basis for the generic package infrastructure. It's a bit complex,
>
> but that Makefile is rather pretty well commented. Also, you can have a
>
> look at the doc:
>
> http://buildroot.org/buildroot.html#add_packages
>
> http://buildroot.org/buildroot.html#generic-reference
>
> Regards,
>
> Yann E. MORIN.
>
> --
>
>
> .-----------------.--------------------.------------------.--------------------.
>
> | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics'
> conspiracy: |
>
> | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
>
> | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
>
> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
>
>
> '------------------------------^-------^------------------^--------------------'
>
>
Thanks, Yann
I do not know the initial motive of this movement, but I prefer the old
approach.
The linux kernel is a special "package". Lots of embedded projects (if not
all of them) will start from a certain version of the kernel and hack the
kernel from there, such as add device drivers etc. Then, put the source code
into a local git server to do version control. Some people argued to use
original tarball plus the patch, but it makes the development procedure very
painful. In the old approach, it is very easy to hack the linux.mk to
checkout the kernel source code directly into the output directory. But, in
the new one. Looks it becomes more complex. The kernel is very big. Check
out with the git, archive it to a tarball, and then extract it to the output
directory for building will waste lots of time. Is there a official solution
(or suggestion) for my situation?

again, thanks a lot.

Raymond
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110712/d36f142d/attachment.html>

  reply	other threads:[~2011-07-12 22:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 20:26 [Buildroot] how BR download the linux kernel now raymond zhao
2011-07-12 20:59 ` Yann E. MORIN
2011-07-12 22:03   ` raymond zhao [this message]
2011-07-13  7:46     ` Thomas Petazzoni
2011-07-13 13:31 raymond zhao
2011-07-13 14:14 ` Thomas Petazzoni
2011-08-23 20:30 ` raymond zhao
2011-09-01  7:12   ` 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='CAAa76NSqWgSvUZEgtpCGvk-Ly69P9wdfSoWz1q2XC=-y7EtKFg@mail.gmail.com' \
    --to=raymond.zhao.ml@gmail.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.