while all it requires on UI side is just the ability to pick a generator in cmake invocation, so that the awesome mingw toolchain (gcc or clang) can be used from msys2 or cygwin.
Options
-G <generator-name> = Specify a build system generator.
Generators
The following generators are available on this platform (* marks default):
MSYS Makefiles = Generates MSYS makefiles.
MinGW Makefiles = Generates a make file for use with
mingw32-make.
12GB:charlielito / install-dlib-python-windows on github ↩︎
Just for my own records, there was this prior topic about this which contains links to further discussions relevant to (and almost like a backstage for) the merge-requests posted above:
I wonder if we could absorb the Visual C++ toolchain into the configure system one of these days, then for each module call a specific Makefile from a central one and so on. This approach is already used by Java in the official JDK for instance, and it makes it very easy to pass specific flags or disable each module individually based on toolchain and OS, something which can quickly become a massive roadblock if done directly in configure for every single possible combination. I’ve heard that there is a wishlist about how the build system could be better, so these are my 2 cents on that, but it would require a Unix environment on Windows to build Python unfortunately