Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] Using a patched kernel
Date: Thu, 11 Oct 2012 09:54:14 +0200	[thread overview]
Message-ID: <50767B26.6090209@relinux.de> (raw)
In-Reply-To: <003701cda713$ad86eb10$0894c130$@net>

Am 10.10.2012 20:18, schrieb Chris Wilkinson:
> Is it possible in BR to use a custom patched version of a Linux kernel
> rather than have it get the standard one? 
Yes, use "source override".

Stephan wrote:
>  Frequently Asked Questions
>  ==========================
>  
> +How can I use sources from my local PC instead of the official tarball?
> +-----------------------------------------------------------------------
> +
> +Just use the "Source Directory Override" mechanism.
> +
> +You have to add a file local.mk to your project.  This file should
> +contain the following definition:
> +
> +<package>_OVERRIDE_SRCDIR = wherever.your.source.lives
> +
> +Then announce this file to buildroot in the "Build options" menu as
> +"location of a package override file".
> +
>  

> successfully built with crosstool-ng-1.16.0 and would like to use that.
Didn't know that crosstool can build kernels;-)

Stephan
> Chris
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

      reply	other threads:[~2012-10-11  7:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 18:18 [Buildroot] Using a patched kernel Chris Wilkinson
2012-10-11  7:54 ` Stephan Hoffmann [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=50767B26.6090209@relinux.de \
    --to=sho@relinux.de \
    --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