From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Christian Stewart <christian@paral.in>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/2] package/libyaml: add host package
Date: Tue, 6 Sep 2022 10:42:53 +0200 [thread overview]
Message-ID: <20220906084253.GR1490660@scaer> (raw)
In-Reply-To: <20220904190218.198854-1-christian@paral.in>
Christian, All,
On 2022-09-04 12:02 -0700, Christian Stewart via buildroot spake thusly:
> Add a Config.in.host to enable the host-libyaml package.
>
> Signed-off-by: Christian Stewart <christian@paral.in>
Following the comment by Thomas, I've marked this two-patch series as
changes-requested in Patchwork.
Regards,
Yann E. MORIN.
> ---
> package/Config.in.host | 1 +
> package/libyaml/Config.in.host | 7 +++++++
> 2 files changed, 8 insertions(+)
> create mode 100644 package/libyaml/Config.in.host
>
> diff --git a/package/Config.in.host b/package/Config.in.host
> index 99edeafece..66b64fd7c6 100644
> --- a/package/Config.in.host
> +++ b/package/Config.in.host
> @@ -47,6 +47,7 @@ menu "Host utilities"
> source "package/jsmin/Config.in.host"
> source "package/kmod/Config.in.host"
> source "package/libp11/Config.in.host"
> + source "package/libyaml/Config.in.host"
> source "package/lld/Config.in.host"
> source "package/lpc3250loader/Config.in.host"
> source "package/lttng-babeltrace/Config.in.host"
> diff --git a/package/libyaml/Config.in.host b/package/libyaml/Config.in.host
> new file mode 100644
> index 0000000000..fd47362a91
> --- /dev/null
> +++ b/package/libyaml/Config.in.host
> @@ -0,0 +1,7 @@
> +config BR2_PACKAGE_HOST_LIBYAML
> + bool "host libyaml"
> + help
> + LibYAML is a YAML 1.1 parser and emitter written in C.
> + Host package.
> +
> + http://pyyaml.org/wiki/LibYAML
> \ No newline at end of file
> --
> 2.37.3
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/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. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-09-06 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 19:02 [Buildroot] [PATCH v1 1/2] package/libyaml: add host package Christian Stewart via buildroot
2022-09-04 19:02 ` [Buildroot] [PATCH v1 2/2] package/python-pyyaml: " Christian Stewart via buildroot
2022-09-05 7:05 ` [Buildroot] [PATCH v1 1/2] package/libyaml: " Thomas Petazzoni via buildroot
2022-09-05 7:07 ` Christian Stewart via buildroot
2022-09-05 7:16 ` Thomas Petazzoni via buildroot
2022-09-06 8:42 ` Yann E. MORIN [this message]
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=20220906084253.GR1490660@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=christian@paral.in \
--cc=thomas.petazzoni@bootlin.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