From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/2] Include makefiles from GLOBAL_PATCH_DIR
Date: Sat, 5 Sep 2020 22:32:13 +0200 [thread overview]
Message-ID: <20200905203213.GA14354@scaer> (raw)
In-Reply-To: <20191109185512.24139-1-jeremy.rosen@smile.fr>
J?r?my, All,
On 2019-11-09 19:55 +0100, J?r?my Rosen spake thusly:
> V2:
> * fix includes happening multiple times on host+target packages
> * change name of included makefiles from .mk to .smk (see commit for
> details)
>
> Note that the first patch might be usefull independently of the (more
> controversial) second patch.
>
> I am opened to changing the .smk to any pattern you suggest
> I am not sure where to fit this in the documentation. suggestions
> welcomed
As was discussed when we met in Lyon, and elsewhere on the list (sorry,
I can't dig the thread now), we already outlined a better solution,
which is to provide a generic way for a package to be extended or even
completely overriden from a br2-external tree.
I know it's been quite a long time, but I hope you do remember that
discussion, and hopefully you can also dig the thread on the list...
I've now marked that series as rejected.
Thanks.
> J?r?my Rosen (2):
> allow .smk files as includes in packages
> Include makefiles from GLOBAL_PATCH_DIR
>
> package/pkg-autotools.mk | 1 +
> package/pkg-cmake.mk | 1 +
> package/pkg-generic.mk | 8 ++++++--
> package/pkg-golang.mk | 1 +
> package/pkg-kconfig.mk | 1 +
> package/pkg-kernel-module.mk | 1 +
> package/pkg-luarocks.mk | 1 +
> package/pkg-meson.mk | 1 +
> package/pkg-perl.mk | 1 +
> package/pkg-python.mk | 1 +
> package/pkg-rebar.mk | 1 +
> package/pkg-utils.mk | 21 ++++++++++++++++++++-
> package/pkg-virtual.mk | 1 +
> package/pkg-waf.mk | 1 +
> 14 files changed, 38 insertions(+), 3 deletions(-)
>
> --
> 2.24.0.rc1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-09-05 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 18:55 [Buildroot] [PATCH v2 0/2] Include makefiles from GLOBAL_PATCH_DIR Jérémy Rosen
2019-11-09 18:55 ` [Buildroot] [PATCH v2 1/2] allow .smk files as includes in packages Jérémy Rosen
2019-11-09 18:55 ` [Buildroot] [PATCH v2 2/2] Include makefiles from GLOBAL_PATCH_DIR Jérémy Rosen
2020-09-05 20:32 ` Yann E. MORIN [this message]
2020-09-07 7:17 ` [Buildroot] [PATCH v2 0/2] " Jérémy ROSEN
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=20200905203213.GA14354@scaer \
--to=yann.morin.1998@free.fr \
--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