> How come GCC is not one of the tested compilers on Windows
For good or bad historic reasons, GDAL on Windows is mostly built with MSVC.
A good reason to use MSVC is when you want to link against C++ libraries that
are also build
with MSVC, due to different symbol manglings between GCC and MSV
Just an innocent question...
How come GCC is not one of the tested compilers on Windows and it's the
only tested compiler for Linux?
Is GCC for Windows not in par with MSVC?
Idan
On Thu, 4 Jun 2020 at 01:41, Even Rouault
wrote:
> On lundi 20 avril 2020 20:16:41 CEST Howard Butler wrote:
>
> > >
On lundi 20 avril 2020 20:16:41 CEST Howard Butler wrote:
> > On Apr 16, 2020, at 7:46 PM, Mateusz Loskot wrote:
> >
> > On Fri, 17 Apr 2020 at 01:45, Mike Taves wrote:
> >> It seems that many projects have shifted from AppVeyor to AZP for
> >> performance benefits.
> >
> > Or GitHub Actions, w
> On Apr 16, 2020, at 7:46 PM, Mateusz Loskot wrote:
>
> On Fri, 17 Apr 2020 at 01:45, Mike Taves wrote:
>>
>> It seems that many projects have shifted from AppVeyor to AZP for
>> performance benefits.
>
> Or GitHub Actions, which is an incarnation of AzP.
Having done both GitHub Actions an
Hi Even,
I would vote for removing the VS2015 testing.
-jeff
On 2020-04-16 8:16 p.m., Even Rouault wrote:
Hi,
I've been a bit frustrated lately by the time spent on the GDAL AppVeyor
CI builds: roughly 50 minutes for each of the two configs we test, VS
2017 x86 and VS 2015 x64, which can
On Fri, 17 Apr 2020 at 01:45, Mike Taves wrote:
>
> It seems that many projects have shifted from AppVeyor to AZP for
> performance benefits.
Or GitHub Actions, which is an incarnation of AzP.
> As you mentioned, some of the dependencies could be built and cached,
> rather than using vcpkg.
cac
Hi Even,
Yes, I agree these times are way longer than they should take.
It looks like Howard was investigating AZP:
https://github.com/OSGeo/PROJ/tree/azp how is that going?
It seems that many projects have shifted from AppVeyor to AZP for
performance benefits.
As you mentioned, some of the dep
Hi,
I've been a bit frustrated lately by the time spent on the GDAL AppVeyor CI
builds: roughly 50
minutes for each of the two configs we test, VS 2017 x86 and VS 2015 x64, which
can cause
huge delays in case of busy days with many pull requests etc. (those delays
also impact PROJ
since the
