All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to regenerate zImage?
Date: Mon, 26 Nov 2012 09:02:18 +0100	[thread overview]
Message-ID: <20121126090218.69c0b3af@skate> (raw)
In-Reply-To: <CAAsE_ud49Ku0NKg-8Ku1mbMXVxkSfLNefvV6pnst2B9GD-4o+A@mail.gmail.com>

Dear Woody Wu,

Please do not reply to me directly: always keep the list Cc'ed.

On Mon, 26 Nov 2012 15:32:52 +0800, Woody Wu wrote:
> > Two solutions:
> >
> >  *) Do the build of the component you're actively working on outside of
> >     Buildroot. Typically, when I do kernel hacking, I do it outside of
> >     Buildroot, and I use Buildroot only as a final integration
> >     mechanism, to make sure that the system build process is
> >     reproducible. But not during development.
> >
> >  *) Use the OVERRIDE_SRCDIR mechanism, as documented in
> >     http://www.elinux.org/images/2/2a/Using-buildroot-real-project.pdf,
> >     slide 41.
> >
> > Best regards,
> >
> > Thomas
> 
> Thanks for the excellent slides.  But I don't understand, where to
> input the "LINUX_OVERRIDE_SRCDIR=/my/path/of/linux".  Did I miss
> something?

You should put it in a file called "local.mk" at the root of the
Buildroot sources directory. Note that "local.mk" is the default
name/location, you can tune that using BR2_PACKAGE_OVERRIDE_FILE.

Best regards,

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

  parent reply	other threads:[~2012-11-26  8:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20  8:17 [Buildroot] How to regenerate zImage? Woody Wu
2012-11-20  9:01 ` Thomas Petazzoni
2012-11-20 11:24   ` Woody Wu
2012-11-21  4:40     ` Woody Wu
2012-11-21  9:38     ` Thomas Petazzoni
     [not found]       ` <CAAsE_ud49Ku0NKg-8Ku1mbMXVxkSfLNefvV6pnst2B9GD-4o+A@mail.gmail.com>
2012-11-26  8:02         ` Thomas Petazzoni [this message]
2012-11-27  1:57           ` Woody Wu
2012-11-27  9:54             ` 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=20121126090218.69c0b3af@skate \
    --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.