qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH 03/18] curl: convert to meson
Date: Thu, 17 Dec 2020 13:05:39 +0100	[thread overview]
Message-ID: <149ff9c4-1e0f-ab92-6f02-592e8081c359@redhat.com> (raw)
In-Reply-To: <CAMxuvaxTdkqtYX79DfnyxHYViu6o54egf50cTCWTYbM_6T1t3A@mail.gmail.com>

On 17/12/20 13:00, Marc-André Lureau wrote:
> 
>         -curl="$default_feature"
>         +curl="auto"
> 
> 
>     What about default_feature=no ?
> 
> 
> Oh got it:
>          $(if test "$default_features" = no; then echo 
> "-Dauto_features=disabled"; fi) \

Yeah, Meson has that feature natively.  The plan is to:

1) remove xxx="$default_features" altogether by moving all options to meson

2) possibly remove xxx="auto" by resurrecting the introspection-based 
command line option parsing script.

Paolo



  reply	other threads:[~2020-12-17 12:06 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17  9:40 [PATCH 00/22] meson: move detection of various libraries to meson.build Paolo Bonzini
2020-12-17  9:40 ` [PATCH 01/18] brlapi: convert to meson Paolo Bonzini
2020-12-17 11:35   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 02/18] curl: remove compatibility code, require 7.29.0 Paolo Bonzini
2020-12-17 10:08   ` Daniel P. Berrangé
2020-12-17 11:48   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 03/18] curl: convert to meson Paolo Bonzini
2020-12-17 10:11   ` Daniel P. Berrangé
2020-12-17 11:59   ` Marc-André Lureau
2020-12-17 12:00     ` Marc-André Lureau
2020-12-17 12:05       ` Paolo Bonzini [this message]
2020-12-17  9:40 ` [PATCH 04/18] glusterfs: " Paolo Bonzini
2020-12-17 12:15   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 05/18] bzip2: " Paolo Bonzini
2020-12-17 12:24   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 06/18] libiscsi: " Paolo Bonzini
2020-12-17 12:25   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 07/18] libnfs: " Paolo Bonzini
2020-12-17 12:26   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 08/18] libssh: " Paolo Bonzini
2020-12-17 12:35   ` Marc-André Lureau
2020-12-17 13:09     ` Paolo Bonzini
2020-12-17  9:40 ` [PATCH 09/18] rbd: " Paolo Bonzini
2020-12-17 12:36   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 10/18] lzo: " Paolo Bonzini
2020-12-17 12:42   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 11/18] snappy: " Paolo Bonzini
2020-12-17 12:47   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 12/18] lzfse: " Paolo Bonzini
2020-12-17 13:11   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 13/18] zstd: " Paolo Bonzini
2020-12-17 13:31   ` Marc-André Lureau
2020-12-17 13:32     ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 14/18] seccomp: " Paolo Bonzini
2020-12-17 13:36   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 15/18] virtfs: " Paolo Bonzini
2020-12-17 13:38   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 16/18] cap_ng: " Paolo Bonzini
2020-12-17 13:54   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 17/18] libattr: " Paolo Bonzini
2020-12-17 14:05   ` Marc-André Lureau
2020-12-17  9:40 ` [PATCH 18/18] meson.build: convert --with-default-devices " Paolo Bonzini
2020-12-17 14:08   ` Marc-André Lureau

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=149ff9c4-1e0f-ab92-6f02-592e8081c359@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=marcandre.lureau@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).