From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 2/2] linux: Add support for specifying a custom directory
Date: Sun, 29 Oct 2017 10:12:49 +0100 [thread overview]
Message-ID: <20171029101249.19a91e32@windsurf> (raw)
In-Reply-To: <20171029072649.GA2899@scaer>
Hello,
On Sun, 29 Oct 2017 08:26:49 +0100, Yann E. MORIN wrote:
> On 2017-10-28 19:06 -0700, Florian Fainelli spake thusly:
> > Add the ability to specify a path to a custom directory where kernel sources
> > may be contained. This is useful when doing kernel development in an existing
> > git tree.
>
> This case is covered by the override-sourcedir mechanism.
>
> Create a file (by default, local.mk) in your config directory (the one
> with the Buildroot .config file), and edit this file with:
>
> LINUX_OVERRIDE_SRCDIR = /path/to/your/linux
>
> and Buildroot will use that as a rsync source, instead of downloading
> the kernel sources.
>
> See also e782cd5b1bc (Revert "Added local directory as source of kernel
> code") for more in-depth explanations. ;-)
Fully agreed with Yann here: there is no point in adding a
Linux-specific solution for this use case, as we already have a much
more general solution that works for all packages, including the
'linux' package.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-29 9:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 2:06 [Buildroot] [RFC 0/2] Add support for specifying a custom kernel directory Florian Fainelli
2017-10-29 2:06 ` [Buildroot] [RFC 1/2] pkg-generic: Don't check for trailing slashes for local method Florian Fainelli
2017-10-29 2:06 ` [Buildroot] [RFC 2/2] linux: Add support for specifying a custom directory Florian Fainelli
2017-10-29 7:26 ` Yann E. MORIN
2017-10-29 9:12 ` Thomas Petazzoni [this message]
2017-10-29 17:26 ` Florian Fainelli
2017-10-29 18:12 ` Yann E. MORIN
2017-10-30 3:27 ` Florian Fainelli
2017-10-30 22:32 ` Yann E. MORIN
2017-11-03 5:03 ` Florian Fainelli
2017-11-03 7:04 ` Yann E. MORIN
2017-11-03 9:23 ` Thomas Petazzoni
2017-10-29 7:33 ` [Buildroot] [RFC 0/2] Add support for specifying a custom kernel directory Yann E. MORIN
2017-10-29 17:10 ` Florian Fainelli
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=20171029101249.19a91e32@windsurf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox