| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: meson "experimental"? |
| Date: | 2024-05-31 10:34:17 |
| Message-ID: | CAJ7c6TMBm+XBMhMnOeiq6C=PXYjhN1kg0oqutCL=UMK_AZaghw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
>> By a quick look on the buildfarm we seem to use Ninja >= 1.11.1.
>> However since Meson can use both Ninja and VS as a backend I'm not
>> certain which section would be most appropriate for naming the minimal
>> required version of Ninja.
>
> When I tried building with the VS backend it blew up, I don't recall the details. I think we should just use ninja everywhere. That keeps things simple. On Windows I just install python and then do "pip install meson ninja"
If we know that it doesn't work I suggest removing mention of
--backend option from [1] until it will, in order to avoid any
confusion.
[1]: https://www.postgresql.org/docs/devel/install-meson.html
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2024-05-31 10:54:03 | Re: Schema variables - new implementation for Postgres 15 |
| Previous Message | Kashif Zeeshan | 2024-05-31 10:27:23 | Re: Switch background worker on/off in runtime. |