Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel and Uboot
Date: Tue, 26 Nov 2013 22:45:00 +0100	[thread overview]
Message-ID: <5295165C.7020708@mind.be> (raw)
In-Reply-To: <OF2C4FAABF.33F2B611-ON85257C2E.0063CAF1-85257C2E.00641111@LocalDomain>

On 25/11/13 19:13, Naitik Amin wrote:
> Hi there,
>
> I am looking to submit my extracted kernel and uboot into my source
> control. Is there a config option in BR that I can use to point to a
> folder that contains the kernel and uboot ? I am constantly changing
> kernel and everytime, I do that I have to unzip, make changes and zip.
> Also its hard to track the changes.

  Take a look at LINUX_OVERRIDE_SRCDIR. It's not currently documented in 
the buildroot manual, but you can read the help text of the "location of 
a package override file" in the "Build options" menu.

A package override file is a short makefile that contains variable 
definitions of the form <pkg>_OVERRIDE_SRCDIR, which allows to tell 
Buildroot to use an existing directory as the source directory for a 
particular package. See the Buildroot documentation for more details on 
this feature.


  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2013-11-26 21:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 18:13 [Buildroot] Kernel and Uboot Naitik Amin
2013-11-26 21:45 ` Arnout Vandecappelle [this message]

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=5295165C.7020708@mind.be \
    --to=arnout@mind.be \
    --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