Re: [RFC] building postgres with meson - v11 - Mailing list pgsql-hackers

From samay sharma
Subject Re: [RFC] building postgres with meson - v11
Date
Msg-id CAJxrbyw3uthKFqWG3Cn1bdzoWN3BkRb+0Y=QtYPom4YnVWrMZQ@mail.gmail.com
Whole thread Raw
In response to Re: [RFC] building postgres with meson - v11  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers


On Tue, Sep 6, 2022 at 9:46 PM Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
On 02.09.22 01:12, samay sharma wrote:
> So, I was thinking of the following structure:
> - Supported Platforms
> - Getting the Source
> - Building with make and autoconf
>    -- Short version
>    -- Requirements
>    -- Installation Procedure and it's subsections
> - Building with Meson
>    -- Short version
>    -- Requirements
>    -- Installation Procedure and it's subsections
> - Post-installation Setup
> - Platform specific notes

I like that.

Attached is a docs-only patch with that structure. We need to update the platform specific notes section to add meson specific nuances. Also, in terms of supported platforms, if there are platforms which work with make but not with meson, we have to add that too.

Regards,
Samay 

> As a follow up patch, we could also try to fit the Windows part into
> this model. We could add a Building with visual C++ or Microsoft windows
> SDK section. It doesn't have a short version but follows the remaining
> template of requirements and installation procedure subsections
> (Building, Cleaning and Installing and Running Regression tests) well.

We were thinking about removing the old Windows build system for PG 16.
Let's see how that goes.  Otherwise, yes, that would be good as well.
Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Reducing the chunk header sizes on all memory context types
Next
From: Jacob Champion
Date:
Subject: Re: [PATCH] Log details for client certificate failures