From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using an external Linux tree
Date: Mon, 15 Feb 2010 17:43:50 +0000 (UTC) [thread overview]
Message-ID: <hlc14m$tmh$1@ger.gmane.org> (raw)
In-Reply-To: 4B792E68.6020907@heig-vd.ch
On 2010-02-15, Marc Garnier <marc.garnier@heig-vd.ch> wrote:
> *Cliff Holden* Cliff.Holden at Atheros.com:
>> I'm somewhat new to buildroot, but have been building kernels
>> for a while. I have a general question:
>>
>> What is the proper procedure for using an external linux
>> kernel tree in the build? Our SCC system (source code
>> control) is set up to have various kernel versions located in
>> a particular location. If I could get buildroot to "point" to
>> this external kernel, it would be helpful.
>>
>> I did try the "advanced" options that allows the specification
>> of a kernel version and an external "patch" file, which is
>> close, but the custom kernel I have is not set up as a set of
>> patches. I would like an option to simply specify the path of
>> the kernel source for the build to use.
>>
>> Any suggestions would be appreciated.
>
> Have you found the solution?
I'd like to do that as well. I can modify my "build" script to
automagically generate patches against a vanilla source tree
each time, but that seems rather obtuse.
--
Grant Edwards grante Yow! Are we live or on
at tape?
visi.com
next prev parent reply other threads:[~2010-02-15 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 11:22 [Buildroot] Using an external Linux tree Marc Garnier
2010-02-15 17:43 ` Grant Edwards [this message]
2010-02-15 18:32 ` William Wagner
-- strict thread matches above, loose matches on Subject: below --
2009-05-11 17:53 Cliff Holden
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='hlc14m$tmh$1@ger.gmane.org' \
--to=grant.b.edwards@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.