On our side, I ran a few tests for an alternative approach:
- Use the graphical interface natively on Windows (using PyQt, and Pyside 2 n the near future)
- Installing the non-graphical portions in the Windows subsystem for Linux (or providing a Docker container with that portion)
I ran a simple test with an Intern in which code_saturne was istalled in the WSL, and we simply copied the GUI Python code to another directory under Windows, and were able to run it using Windows native PyQt. To do things more cleanly will require a bit of additional "cleanup/modularity work" on the GUI/Python code, and some local changes in the build system, but does not require a full build, so we could have that relatively soon.
To do a full, native Windows build, a full revamp of the build system would probably be necessary, and I have no sign of anybody working on that.
Finally, building a full Windows installer would require yet more work, and the main difficulty is keeping it up to date (not actually difficult, but needs to be fully redone if not maintained for a period of time longer than a year or 2).
Were you thinking of of binary installer (need help) or just getting the code to work on Windows (almost there) ?
The discussion can continue on this forum, and if it becomes more specific/active/task oriented, can be continue on the bug-tracker.