[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: |
Paolo Bonzini |
Subject: |
Re: [RFC PATCH 0/3] Automatically convert configure options to meson build options |
Date: |
Mon, 14 Sep 2020 12:27:59 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 |
On 14/09/20 11:57, Stefan Hajnoczi wrote:
> 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?
No, only developers need jq and only if they add configure options.
Using Python would certainly be possible, though probably it wouldn't be
a one-liner as for jq.
Paolo
- [PATCH 2/3] configure: early test for Python, (continued)
- [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, 2020/09/14