From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH v2 1/3] kernel: add make target for the installed device trees
Date: Thu, 31 Aug 2023 12:44:23 +0200 [thread overview]
Message-ID: <20230831104425.2874985-1-rhi@pengutronix.de> (raw)
This makes it easy to depend on the kernel.targetinstall stage by
depending on one of the .dtb's that it installs into the image dir, e.g.
when building a custom recipe for a FIT image. As a nice side-effect,
you can simply call "ptxdist image <board.dtb>" to build the device
tree.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
PATCH v2:
* change ifneq syntax
PATCH v1: https://lore.ptxdist.org/ptxdist/20230822121234.2040303-1-rhi@pengutronix.de
---
rules/kernel.make | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/rules/kernel.make b/rules/kernel.make
index e70af54e6137..a12838bd78ea 100644
--- a/rules/kernel.make
+++ b/rules/kernel.make
@@ -281,6 +281,10 @@ endif
# Target-Install
# ----------------------------------------------------------------------------
+ifneq ($(KERNEL_DTB_FILES),)
+$(addprefix $(IMAGEDIR)/,$(KERNEL_DTB_FILES)): $(STATEDIR)/kernel.targetinstall
+endif
+
$(STATEDIR)/kernel.targetinstall:
@$(call targetinfo)
--
2.39.2
next reply other threads:[~2023-08-31 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 10:44 Roland Hieber [this message]
2023-08-31 10:44 ` [ptxdist] [PATCH v2 2/3] templates: add template for custom FIT images Roland Hieber
2023-08-31 12:07 ` [ptxdist] [PATCH v2] fixup! " Roland Hieber
2023-09-01 6:48 ` [ptxdist] [PATCH v2 2/3] " Michael Olbrich
2023-09-12 10:48 ` Roland Hieber
2023-08-31 10:44 ` [ptxdist] [PATCH v2 3/3] doc: ref_make_macros: document world/image-fit macro Roland Hieber
2023-09-01 6:52 ` [ptxdist] [PATCH v2 1/3] kernel: add make target for the installed device trees Michael Olbrich
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=20230831104425.2874985-1-rhi@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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