From: Jes Sorensen <jes.sorensen@gmail.com>
To: devicetree@vger.kernel.org
Cc: tnovak@meta.com, Jes Sorensen <jes@trained-monkey.org>
Subject: [PATCH 1/1] Skip building dtc if a prebuilt binary is specified via DTC=
Date: Fri, 11 Oct 2024 10:05:07 -0400 [thread overview]
Message-ID: <20241011140507.3703348-2-Jes.Sorensen@gmail.com> (raw)
In-Reply-To: <20241011140507.3703348-1-Jes.Sorensen@gmail.com>
From: Jes Sorensen <jes@trained-monkey.org>
For Android it is common to use a prebuilt dtc, speficied via DTC=. In
this case building dtc as part of the kernel is not necessary, and even
unwanted to avoid mix and match between two different versions of dtc.
Signed-off-by: Jes Sorensen <jes@trained-monkey.org>
---
scripts/dtc/Makefile | 3 +++
1 file changed, 3 insertions(+)
diff --git a/scripts/dtc/Makefile b/scripts/dtc/Makefile
index b47f4daa4515..3b683dc7e582 100644
--- a/scripts/dtc/Makefile
+++ b/scripts/dtc/Makefile
@@ -2,8 +2,11 @@
# scripts/dtc makefile
# *** Also keep .gitignore in sync when changing ***
+# If a prebuilt dtc binary is specificed, don't build dtc
+ifeq ($(DTC),)
hostprogs-always-$(CONFIG_DTC) += dtc fdtoverlay
hostprogs-always-$(CHECK_DTBS) += dtc
+endif
dtc-objs := dtc.o flattree.o fstree.o data.o livetree.o treesource.o \
srcpos.o checks.o util.o
--
2.46.1
next prev parent reply other threads:[~2024-10-11 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 14:05 [RFC PATCH 0/1] Only build dtc when DTC= is not set on the command line Jes Sorensen
2024-10-11 14:05 ` Jes Sorensen [this message]
2024-10-11 22:46 ` [PATCH 1/1] Skip building dtc if a prebuilt binary is specified via DTC= Rob Herring
2024-10-14 14:40 ` Jes Sorensen
2024-10-14 14:48 ` Rob Herring
2024-10-14 14:49 ` Jes Sorensen
2024-10-14 15:17 ` Rob Herring
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=20241011140507.3703348-2-Jes.Sorensen@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jes@trained-monkey.org \
--cc=tnovak@meta.com \
/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;
as well as URLs for NNTP newsgroup(s).