code_saturne User's Forum

Hello to all,

We are happy to provide Windows builds to our users, but the current build system is fragile, and our team is not too familiar with Windows development, so Windows builds tend to be released with some delay.

If anyone on this forum is willing to contribute with this, whether by getting a toolchain and prerequisites running, or suggesting and implementing a new approach, they are welcome.

Hoping someone can help here.

Best regards,

Yvan

For Windows 10 users, the Linux subsystem for Windows is the best option.

A native Windows build of the GUI combined with a (non-graphical) build of the other parts of the system would avoid the requirement for an X server. A web-based version of the GUI would also do here. We are working on improving the back-end of the GUI, but any help on the front-end would be appreciated.

Update: the Windows builds are not provided anymore (since v6.0/2019):

- they were build using CygWin/Mingw, but the HDF5 library (required for MED en CGNS mesh libraries) became unsupported on that platform (requiring either pure Windows, or full Cygwin or Linux)
* providing a build which cannot read meshes generated by a large fraction of meshing tools is not so useful anymore

- the build machine and environment was obsolete and has been retired. Due to lack of interest/need/manpower/priority, it was not replaced.

Building on modern Windows WSL works fine. We may work on containerized versions in the future, but have no spceific timeline for this. So contributions for other build types are welcome.

Hello,

Thank for your feedback.

This solution has also been used on our side, especially in some courses with Students at schools which have WSL installs but no native Linux machines. I have not checked, but from what I have read, more recent versions of WSL2 might even allow the GUI to work without a separate X server.

A solution considered would also be to adapt the GUI so it can be installed directly on Windows (basically copying the Linux installed directory on Windows), an running the GUI on native Windows and the non-graphical part on WSL. It has been tested with a few manual edits, and works, but no install using this solution is automated yet.

So if some Windows fan has time on their hands and wants to work on a more "native" Windows version, they are still welcome. Otherwise, WSL is a practical solution.

Best regards,

Yvan