From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 7/8] meson: Display cryto-related information altogether
Date: Thu, 21 Jan 2021 10:11:27 +0000 [thread overview]
Message-ID: <20210121101127.GF3125227@redhat.com> (raw)
In-Reply-To: <20210121095616.1471869-8-philmd@redhat.com>
On Thu, Jan 21, 2021 at 10:56:15AM +0100, Philippe Mathieu-Daudé wrote:
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> Cc: Daniel P. Berrange <berrange@redhat.com>
> ---
> meson.build | 34 +++++++++++++++++++---------------
> 1 file changed, 19 insertions(+), 15 deletions(-)
>
> diff --git a/meson.build b/meson.build
> index e372b69f163..9274775a81a 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -2453,19 +2453,8 @@
> endif
> summary(summary_info, bool_yn: true, section: 'Block layer support')
>
> +# Crypto
Rather than a comment why not introduce grouping in the output
so it is visible when reading the summary.
This can be done in meson by calling summary() multiple times
giving "section: 'Crypto'" arg.
> summary_info = {}
> -summary_info += {'sparse enabled': sparse.found()}
> -if targetos == 'darwin'
> - summary_info += {'Cocoa support': cocoa.found()}
> -endif
> -# TODO: add back version
> -summary_info += {'SDL support': sdl.found()}
> -summary_info += {'SDL image support': sdl_image.found()}
> -# TODO: add back version
> -summary_info += {'GTK support': gtk.found()}
> -summary_info += {'pixman': pixman.found()}
> -# TODO: add back version
> -summary_info += {'VTE support': config_host.has_key('CONFIG_VTE')}
> summary_info += {'TLS priority': config_host['CONFIG_TLS_PRIORITY']}
> summary_info += {'GNUTLS support': config_host.has_key('CONFIG_GNUTLS')}
> # TODO: add back version
> @@ -2479,6 +2468,24 @@
> if config_host.has_key('CONFIG_NETTLE')
> summary_info += {' XTS': not config_host.has_key('CONFIG_QEMU_PRIVATE_XTS')}
> endif
> +summary_info += {'crypto afalg': config_host.has_key('CONFIG_AF_ALG')}
> +summary_info += {'rng-none': config_host.has_key('CONFIG_RNG_NONE')}
> +summary_info += {'Linux keyring': config_host.has_key('CONFIG_SECRET_KEYRING')}
> +summary(summary_info, bool_yn: true, section: 'Crypto')
> +
> +summary_info = {}
> +summary_info += {'sparse enabled': sparse.found()}
> +if targetos == 'darwin'
> + summary_info += {'Cocoa support': cocoa.found()}
> +endif
> +# TODO: add back version
> +summary_info += {'SDL support': sdl.found()}
> +summary_info += {'SDL image support': sdl_image.found()}
> +# TODO: add back version
> +summary_info += {'GTK support': gtk.found()}
> +summary_info += {'pixman': pixman.found()}
> +# TODO: add back version
> +summary_info += {'VTE support': config_host.has_key('CONFIG_VTE')}
> summary_info += {'libtasn1': config_host.has_key('CONFIG_TASN1')}
> summary_info += {'PAM': config_host.has_key('CONFIG_AUTH_PAM')}
> summary_info += {'iconv support': iconv.found()}
> @@ -2531,7 +2538,6 @@
> summary_info += {'QGA MSI support': config_host.has_key('CONFIG_QGA_MSI')}
> endif
> summary_info += {'seccomp support': seccomp.found()}
> -summary_info += {'crypto afalg': config_host.has_key('CONFIG_AF_ALG')}
> summary_info += {'GlusterFS support': glusterfs.found()}
> summary_info += {'TPM support': config_host.has_key('CONFIG_TPM')}
> summary_info += {'libssh support': config_host.has_key('CONFIG_LIBSSH')}
> @@ -2547,8 +2553,6 @@
> summary_info += {'libpmem support': config_host.has_key('CONFIG_LIBPMEM')}
> summary_info += {'libdaxctl support': config_host.has_key('CONFIG_LIBDAXCTL')}
> summary_info += {'libudev': libudev.found()}
> -summary_info += {'rng-none': config_host.has_key('CONFIG_RNG_NONE')}
> -summary_info += {'Linux keyring': config_host.has_key('CONFIG_SECRET_KEYRING')}
> summary(summary_info, bool_yn: true, section: 'Misc')
>
> if not supported_cpus.contains(cpu)
> --
> 2.26.2
>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-01-21 10:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 9:56 [PATCH v2 0/8] meson: Clarify summary Philippe Mathieu-Daudé
2021-01-21 9:56 ` [PATCH v2 1/8] meson: Summarize information related to directories first Philippe Mathieu-Daudé
2021-01-21 9:56 ` [PATCH v2 2/8] meson: Display host binaries information altogether Philippe Mathieu-Daudé
2021-01-21 9:56 ` [PATCH v2 3/8] meson: Summarize overall features altogether Philippe Mathieu-Daudé
2021-01-21 9:56 ` [PATCH v2 4/8] meson: Summarize compilation-related information altogether Philippe Mathieu-Daudé
2021-01-21 9:56 ` [PATCH v2 5/8] meson: Display accelerators and selected targets altogether Philippe Mathieu-Daudé
2021-01-21 9:56 ` [RFC PATCH v2 6/8] meson: Display block layer information altogether Philippe Mathieu-Daudé
2021-01-21 9:56 ` [PATCH v2 7/8] meson: Display cryto-related " Philippe Mathieu-Daudé
2021-01-21 9:58 ` Philippe Mathieu-Daudé
2021-01-21 10:11 ` Daniel P. Berrangé [this message]
2021-01-21 10:13 ` Daniel P. Berrangé
2021-01-21 11:01 ` Philippe Mathieu-Daudé
2021-01-21 9:56 ` [PATCH v2 8/8] meson: Display library dependencies altogether Philippe Mathieu-Daudé
2021-01-21 12:03 ` [PATCH v2 0/8] meson: Clarify summary Paolo Bonzini
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=20210121101127.GF3125227@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).