At one time in a build every job worked on master_andre with everything Visual Studio 2022
However, when I attempted everything Visual Studio 2022 on master(postgres-plr),
the end result was Visual Studio 2017 for plr on pg 11 and greater.
and
Visual Studio 2015 for plr on pg 10
Assume the old bad (but well done) detection of the duplicate "plr" entries in the msvc Visual Studio 2019+ build
are still happening.
I NEED to build plr BY HAND LOCALLY AND manually using this repository appveyor.yml methods and come up with a regular expression or R de-duplication to remove that duplicate entry in the msvc builds SO THAT I can get the builds to work on Visual Studio 2019+ (I mean 2022+).
At one time in a build every job worked on master_andre with everything Visual Studio 2022
However, when I attempted everything Visual Studio 2022 on master(postgres-plr), the end result was Visual Studio 2017 for plr on pg 11 and greater. and Visual Studio 2015 for plr on pg 10
Assume the old bad (but well done) detection of the duplicate "plr" entries in the msvc Visual Studio 2019+ build are still happening.
I NEED to build plr BY HAND LOCALLY AND manually using this repository appveyor.yml methods and come up with a regular expression or R de-duplication to remove that duplicate entry in the msvc builds SO THAT I can get the builds to work on Visual Studio 2019+ (I mean 2022+).