From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: meson vs tarballs |
Date: | 2024-03-13 07:40:42 |
Message-ID: | e416b082-dea5-4440-90c9-ac7ff15d9509@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 13.03.24 07:42, Andrew Dunstan wrote:
> On 2024-03-13 We 02:31, Andrew Dunstan wrote:
>> On 2024-03-13 We 02:22, Peter Eisentraut wrote:
>>> On 13.03.24 07:11, Andrew Dunstan wrote:
>>>> I and several colleagues have just been trying to build from a
>>>> tarball with meson.
>>>
>>>> That seems pretty awful and unfriendly and I didn't see anything
>>>> about it in the docs.
>>>
>>> At https://www.postgresql.org/docs/16/install-requirements.html is says:
>>>
>>> """
>>> Alternatively, PostgreSQL can be built using Meson. This is currently
>>> experimental and only works when building from a Git checkout (not
>>> from a distribution tarball).
>>> """
>>
>> Ah!. Darn, I missed that. Thanks.
> Of course, when release 17 comes out this had better not be the case,
> since we have removed the custom Windows build system.
Yes, this has been changed in 17.
From | Date | Subject | |
---|---|---|---|
Next Message | Anton A. Melnikov | 2024-03-13 07:41:45 | Re: Add the ability to limit the amount of memory that can be allocated to backends. |
Previous Message | Andy Fan | 2024-03-13 07:39:07 | Re: a wrong index choose when statistics is out of date |