All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Knight <git@jdknight.me>
To: buildroot@buildroot.org
Cc: James Knight <git@jdknight.me>
Subject: [Buildroot] [PATCH 1/1] Makefile: ignore configs/ prefix on configuration events
Date: Sun, 29 Jun 2025 22:38:26 -0400	[thread overview]
Message-ID: <20250630023826.1163-1-git@jdknight.me> (raw)

Allows accepting board configuration events that are prefixed with a
`configs/` path. This provides a convenience for users where it can be
slightly easier/quicker to utilize shell completion to prepare a build.
For example:

    make configs/qemu_sparc64_sun4u_defconfig

Would be equivalent to:

    make qemu_sparc64_sun4u_defconfig

Signed-off-by: James Knight <git@jdknight.me>
---
 Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index c581067320..46b246245b 100644
--- a/Makefile
+++ b/Makefile
@@ -1026,7 +1026,7 @@ defconfig: $(BUILD_DIR)/buildroot-config/conf outputmakefile
 		$(firstword \
 			$(foreach d, \
 				$(call reverse,$(TOPDIR) $(BR2_EXTERNAL_DIRS)), \
-				$(wildcard $(d)/configs/$@) \
+				$(wildcard $(d)/configs/$(@:configs/%=%)) \
 			) \
 		), \
 		$(error "Can't find $@") \
-- 
2.49.0.windows.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2025-06-30  2:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30  2:38 James Knight [this message]
2025-06-30  7:48 ` [Buildroot] [PATCH 1/1] Makefile: ignore configs/ prefix on configuration events Edgar Bonet via buildroot
2025-07-01  7:04   ` Arnout Vandecappelle via buildroot
2025-07-01  7:51     ` Edgar Bonet via buildroot
2025-07-01  7:02 ` Arnout Vandecappelle via buildroot
2025-07-07  1:30   ` James Knight

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=20250630023826.1163-1-git@jdknight.me \
    --to=git@jdknight.me \
    --cc=buildroot@buildroot.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.