From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/5] system: support br2-external skeleton packages
Date: Wed, 14 Oct 2020 23:17:30 +0200 [thread overview]
Message-ID: <20201014211730.GD3466@scaer> (raw)
In-Reply-To: <20201013223605.188920-1-brandon.maier@rockwellcollins.com>
Brandon, All,
On 2020-10-13 17:36 -0500, Brandon Maier spake thusly:
> Today, the BR2_ROOTFS_SKELETON_CUSTOM is the only way to build a custom
> skeleton. But it's limiting as users must provide a pre-built skeleton
> for each target. Supporting a br2-external package allows users to build
> up a skeleton and customize it with their own KConfig options.
>
> Signed-off-by: Brandon Maier <brandon.maier@rockwellcollins.com>
Series applied to master, thanks!
I only did very minor tweaks; please see the ammended commit logs.
Regards,
Yann E. MORIN.
> ---
> support/scripts/br2-external | 9 +++++++++
> system/Config.in | 3 +++
> 2 files changed, 12 insertions(+)
>
> diff --git a/support/scripts/br2-external b/support/scripts/br2-external
> index ededd2d900..01804e1220 100755
> --- a/support/scripts/br2-external
> +++ b/support/scripts/br2-external
> @@ -161,6 +161,7 @@ do_kconfig() {
> toolchains
> jpeg
> openssl
> + skeleton
> )
>
> for br2 in "${items[@]}"; do
> @@ -224,6 +225,14 @@ do_kconfig() {
> else
> printf '# No openssl from: %s\n\n' "${br2_desc}"
> fi >>"${outputdir}/.br2-external.in.openssl"
> +
> + if [ -f "${br2_ext}/provides/skeleton.in" ]; then
> + printf 'comment "skeleton from: %s"\n' "${br2_desc}"
> + printf 'source "%s/provides/skeleton.in"\n' "${br2_ext}"
> + printf '\n'
> + else
> + printf '# No skeleton from: %s\n\n' "${br2_desc}"
> + fi >>"${outputdir}/.br2-external.in.skeleton"
> done
>
> printf 'endmenu\n' >>"${outputdir}/.br2-external.in.menus"
> diff --git a/system/Config.in b/system/Config.in
> index b8b7c16529..a363e099e5 100644
> --- a/system/Config.in
> +++ b/system/Config.in
> @@ -23,6 +23,9 @@ config BR2_ROOTFS_SKELETON_CUSTOM
> help
> Use custom target skeleton.
>
> +# skeleton from br2-external trees, if any
> +source "$BR2_BASE_DIR/.br2-external.in.skeleton"
> +
> endchoice
>
> if BR2_ROOTFS_SKELETON_CUSTOM
> --
> 2.28.0
>
--
.-----------------.--------------------.------------------.--------------------.
| 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-10-14 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 19:41 [Buildroot] [PATCH 1/2] system: Move skeleton-init-* selection to init Brandon Maier
2020-10-13 19:41 ` [Buildroot] [PATCH 2/2] system: support br2-external init systems Brandon Maier
2020-10-13 22:36 ` [Buildroot] [PATCH v2 1/5] system: support br2-external skeleton packages Brandon Maier
2020-10-14 21:17 ` Yann E. MORIN [this message]
2020-10-13 22:36 ` [Buildroot] [PATCH v2 2/5] docs/manual: add section about br2-external skeleton Brandon Maier
2020-10-13 22:36 ` [Buildroot] [PATCH v2 3/5] system: Move skeleton-init-* selection to init Brandon Maier
2020-10-13 22:36 ` [Buildroot] [PATCH v2 4/5] system: support br2-external init systems Brandon Maier
2020-10-13 22:36 ` [Buildroot] [PATCH v2 5/5] docs/manual: add section about br2-external init Brandon Maier
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=20201014211730.GD3466@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 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.