Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Garnier <marc.garnier@heig-vd.ch>
To: buildroot@busybox.net
Subject: [Buildroot] Using an external Linux tree
Date: Mon, 15 Feb 2010 12:22:16 +0100	[thread overview]
Message-ID: <4B792E68.6020907@heig-vd.ch> (raw)

Hi,

Have you found the solution?

*Cliff Holden* Cliff.Holden at Atheros.com 
<mailto:buildroot%40busybox.net?Subject=Re%3A%20%5BBuildroot%5D%20Using%20an%20external%20Linux%20tree&In-Reply-To=%3CD302D58E77B2A2448F54114C6F143271EC45E9F17E%40SC1EXMB-MBCL.global.atheros.com%3E>
/Mon May 11 17:53:32 UTC 2009/
------------------------------------------------------------------------

Hi all,

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.

Thanks!!


-- 
///////////////////////////////////////////// 
Marc Garnier
R&D Certified Engineer

eMbedded Information Systems Institute (MIS)
University of Applied Sciences, Vaud
rue Galil?e 15
1400 Yverdon-les-Bains
Switzerland

Tel : +41 (0)24 423 97 71
Fax : +41 (0)24 423 97 59
URL : http://mis.heig-vd.ch

             reply	other threads:[~2010-02-15 11:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 11:22 Marc Garnier [this message]
2010-02-15 17:43 ` [Buildroot] Using an external Linux tree Grant Edwards
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=4B792E68.6020907@heig-vd.ch \
    --to=marc.garnier@heig-vd.ch \
    --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