From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Arnout Vandecappelle <arnout@rnout.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] Makefile: allow defconfig to be in a sub-directory
Date: Fri, 16 May 2025 20:26:20 +0200 [thread overview]
Message-ID: <aCeDTLbUoczbZXLK@landeda> (raw)
In-Reply-To: <cc7f2887-8508-42d3-bfb5-e76333075429@rnout.be>
Arnout, All,
On 2025-05-16 19:46 +0200, Arnout Vandecappelle spake thusly:
> On 15/05/2025 23:18, Yann E. MORIN wrote:
> > Currently, the defconfigs must all live in the top-level configs/
[--SNIP--]
> It is actually only about list-defconfigs, so I rephrased:
Right.
> Makefile: include defconfigs in sub-directories in list-defconfigs
>
> Currently, list-defconfigs only lists the defconfigs that live
> live in the top-level configs/ directory. For the in-tree defconfigs
Spurious leading space; double 'live'. But no worries, I could have been
the one doing those typoes. ;-)
Thanks! :-)
Regards,
Yann E. MORIN.
> this is indeed the case, but it is possible to manage the configs in a
> br2-external tree with sub-directories.
>
> A few examples:
> - for a given board, a first defconfig is the full system, and a
> second is the rescue system;
> - for a given board, two defconfigs implement an A/B feature set;
> - a set of configurations targetting various famillies of systems each
> running on different hardware, sorted per familly.
>
> Extend list-defconfigs to look for and report defconfigs in
> sub-directories of the top-level configs/.
>
>
>
> Applied to master, thanks.
>
> Regards,
> Arnout
>
>
> >
> > Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> > ---
> > Makefile | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/Makefile b/Makefile
> > index 411e1de515..c0a41cabd5 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -1218,7 +1218,7 @@ help:
> > # $(2): br2-external name, empty for bundled
> > define list-defconfigs
> > @first=true; \
> > - for defconfig in $(1)/configs/*_defconfig; do \
> > + for defconfig in $$(find $(1)/configs -name '*_defconfig' |sort); do \
> > [ -f "$${defconfig}" ] || continue; \
> > if $${first}; then \
> > if [ "$(2)" ]; then \
> > @@ -1228,7 +1228,7 @@ define list-defconfigs
> > fi; \
> > first=false; \
> > fi; \
> > - defconfig="$${defconfig##*/}"; \
> > + defconfig="$${defconfig#$(1)/configs/}"; \
> > printf " %-35s - Build for %s\n" "$${defconfig}" "$${defconfig%_defconfig}"; \
> > done; \
> > $${first} || printf "\n"
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-05-16 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 21:18 [Buildroot] [PATCH] Makefile: allow defconfig to be in a sub-directory Yann E. MORIN
2025-05-16 17:46 ` Arnout Vandecappelle via buildroot
2025-05-16 18:26 ` Yann E. MORIN [this message]
2025-05-31 16:53 ` Arnout Vandecappelle via buildroot
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=aCeDTLbUoczbZXLK@landeda \
--to=yann.morin.1998@free.fr \
--cc=arnout@rnout.be \
--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.