[gdal-dev] Windows CI build times

[Even Rouault]

> 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 MSVC (particularly the 
proprietary ones that can't be rebuilt from source).
(I've heard that recent clang versions on Windows can use MSVC C++ symbol mangling, so 
things could in theory be smoother now.)

Actually, we have a CI target uses the mingw32 cross compiler from Linux, so that halfs count 
for testing GCC on Windows. It doesn't test drivers with external library requirements 
though, neither MSYS2 specific issues.

The number of CI configs for GDAL is already quite (too?) big, and as I mentioned in this 
thread, we struggled with build times before the partial migration to github workflows. I'm 
moderately enthusiastic about adding a new one for GCC on Windows. At least it would need 
someone comitted to set it up and maintain it.

> and it's the only tested compiler for Linux?

clang is also tested

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20200625/dee6e67c/attachment.html>