Re: [RFC PATCH 0/3] configure: create a python venv and install meson

2023-03-31 Thread Paolo Bonzini
On 3/30/23 16:11, John Snow wrote: * undo the meson parts from PATCH 3; make patch 3 create the venv + subsume the MKVENV parts of the Makefiles + always set explicit_python=yes (so that at this point the in-tree meson is always used). * add a patch that starts rejecting --me

Re: [RFC PATCH 0/3] configure: create a python venv and install meson

2023-03-30 Thread John Snow
On Wed, Mar 29, 2023, 9:02 AM Paolo Bonzini wrote: > Thanks for posting this! > > On 3/28/23 23:11, John Snow wrote: > > This series is in RFC state; some notable things: > > - So far, only meson is included in this setup. > > - There's a ton of debugging prints everywhere. It's extremely chatty

Re: [RFC PATCH 0/3] configure: create a python venv and install meson

2023-03-29 Thread Paolo Bonzini
Thanks for posting this! On 3/28/23 23:11, John Snow wrote: This series is in RFC state; some notable things: - So far, only meson is included in this setup. - There's a ton of debugging prints everywhere. It's extremely chatty right now. - Sphinx and qemu.qmp are not yet included in this venv.

[RFC PATCH 0/3] configure: create a python venv and install meson

2023-03-28 Thread John Snow
This patch series creates a mandatory venv during configure time and uses it to install meson. The eventual point of this is to ensure that the Python used to run meson is the same Python used to run Sphinx, tests, and any build-time scripting we have. As it stands, meson and sphinx (and their ext