public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jonathan S. Katz <[email protected]>
To: Andres Freund <[email protected]>
To: [email protected]
To: Tom Lane <[email protected]>
To: Peter Geoghegan <[email protected]>
To: Andrew Dunstan <[email protected]>
To: Amit Kapila <[email protected]>
To: Alvaro Herrera <[email protected]>
Subject: Re: When to drop src/tools/msvc support
Date: Sat, 8 Apr 2023 15:19:20 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
On 4/8/23 3:10 PM, Andres Freund wrote:
> Hi,
>
> I'd planned to write this soon anyway, but it was just brought up in [1].
>
> Originally we had planned to drop src/tools/msvc support shortly after meson
> went in. Unfortunately, it took a bit longer than originally hoped for to
> merge meson support and then longer than hoped to add buildfarm support. I
> don't think there's been any buildfarm client release with meson support yet -
> but we do have windows buildfarm animals using it.
>
> Do we want to drop src/tools/msvc support in 16 (i.e. now), or do it early in
> 17?
>
> I do have a set of patches removing src/tools/msvc. There are a few loose ends
> that I know of (my eyes glaze over every time I try to reconcile the
> src/tools/perl.m4 comments with the referenced comments in Mkvcbuild.pm), and
> probably more small references that grep terms didn't find.
(reads [1])
Can we treat this as an "open item" for completing the transition to
meson for builds as part of v16?
With my personal hat on, it seems silly to wait until v17 to do this,
and I don't see why we would want to wait. If there's limited risk in
doing this and it'll make our builds both more stable + faster, it seems
like we should just do it.
Thanks,
Jonathan
Attachments:
[application/pgp-signature] OpenPGP_signature (840B, ../[email protected]/2-OpenPGP_signature)
download
view thread (21+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: When to drop src/tools/msvc support
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox