[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH 0/3] Automatically convert configure options to meson bui
From: |
Stefan Hajnoczi |
Subject: |
Re: [RFC PATCH 0/3] Automatically convert configure options to meson build options |
Date: |
Mon, 14 Sep 2020 10:57:53 +0100 |
On Sun, Sep 13, 2020 at 12:05:31PM +0200, Paolo Bonzini wrote:
> - because we parse command-line options before meson is available,
> the introspection output is stored in the source tree. The output
> is slightly modified using the "jq" tool in order to ensure that it's
> stable and that modifications to meson_buildoptions.txt do not cause
> horrible conflicts. This is the main reason for the unattractive
> diffstat (the number of JSON lines added is higher than the number
> of configure lines removed, though of course the latter are code
> that must be maintained manually and the former is not).
Does this add a build dependency on jq? Is it possible to use a Python
script or even a command-line one-liner instead?
signature.asc
Description: PGP signature
- [RFC PATCH 0/3] Automatically convert configure options to meson build options, Paolo Bonzini, 2020/09/13
- [PATCH 1/3] configure: quote command line arguments in config.status, Paolo Bonzini, 2020/09/13
- [PATCH 2/3] configure: early test for Python, Paolo Bonzini, 2020/09/13
- [PATCH 3/3] configure: automatically parse command line for meson -D options, Paolo Bonzini, 2020/09/13
- Re: [RFC PATCH 0/3] Automatically convert configure options to meson build options, Yonggang Luo, 2020/09/13
- Re: [RFC PATCH 0/3] Automatically convert configure options to meson build options, Daniel P . Berrangé, 2020/09/14
- Re: [RFC PATCH 0/3] Automatically convert configure options to meson build options,
Stefan Hajnoczi <=