From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Rebuilding Linux after modifying Linux device tree in output/build directory?
Date: Fri, 15 Nov 2019 21:13:40 +0100 [thread overview]
Message-ID: <20191115211340.3c06fe96@windsurf> (raw)
In-Reply-To: <d508ce60a63d4182a02ddfadaeb042ac@EX13D04UEA001.ant.amazon.com>
Hello,
On Fri, 15 Nov 2019 19:40:09 +0000
"Whitney, Scott" <scwhitn@amazon.com> wrote:
> I need to run some experiments where I may need to make a number of
> minor modifications to the Linux Device tree, for example to change
> PWM outputs to GPIO outputs, add some extra GPIO inputs, etc.
>
> Is there a way that I can force a minimal rebuild based on such a
> local change? Buildroot does not seem to keep track of many
> dependencies to trigger a rebuild such as the DTS file being newer
> than the Linux image.
>
> Is "make linux-rebuild" a viable option, or is there a better way to
> rebuild only what is required due to the Device Tree change?
Running "make linux-rebuild" is what you want. It will rebuild just the
kernel, but not from scratch: it will simply run "make" in the kernel
source tree, so only the files you have changed will be rebuilt.
However, be careful: output/build/linux-<version>/ is a "temporary"
directory: the next time you run "make clean", it will be removed, and
all your changes will be lost. So, doing changes directly in
output/build/linux-<version>/ is only good for quick local hacks.
For more serious development, I'd recommend looking at using the
<pkg>_OVERRIDE_SRCDIR mechanism.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-15 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 19:40 [Buildroot] Rebuilding Linux after modifying Linux device tree in output/build directory? Whitney, Scott
2019-11-15 20:13 ` Thomas Petazzoni [this message]
[not found] ` <1573850449466.42632@amazon.com>
2019-11-15 21:02 ` 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=20191115211340.3c06fe96@windsurf \
--to=thomas.petazzoni@bootlin.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