Native Windows binaries using MSYS2

assigned to @Pawan

Hi @Pawan - if you have any immediate ideas/workarounds etc, please add notes here.

Hi
i)Please note that binaries has been cross compiled in Linux environment using mingw-tool chain.
We have not compiled it directly on MSYS2. Error you are getting is more to do msmpi i.e
it shows msmpi is not installed.

ii) MSMPI is bundled with installer but can be installed only when running via admin mode.
MSMPI can be downloaded from this location but separately need to be installed but
again it require, admin permission to do so. msmpi

Regards
Pawan

So any idea how I can fix the above issues?

P.S. As a side note, why not deliver OpenFOAM as an MSYS2/MinGW package that can be installed via pacman/mingw-get?

Please ask your IT to install msmpi in your system. It is provided by microsoft and they should have no issue to install it.
Regarding MSYS2 installed by pacman etc, we can look into it but it will get expedited if some one fund that work

So no way to use the software without MSMPI being installed?!

Based on my knowledge, yes, no other way .

I am no expert, but why not use the available MSYS2/MinGW MSMPI packages? they do not require admin privileges AFIK.

Thanks. I will try that.

Ideally, it would be great if we could have PortableApps and/or Chocolatey packages to have a painless installation of OpenFOAM on Windows OS. Please consider that a huge portion of your potential users work on a machine without admin privileges and asking IT for these sorts of installations doesn't help.

added community label

As a follow-up on this discussion: I was informed here on OpenFOAM discord about this great effort to compile OpenFOAM with Microsoft Visual Studio.

I did see a thread on cfd-online, but was still waiting for a response. Not sure why the person felt the need to rip out most of the copyright and license notices (a clear GPL violation). Some of the changes seem spurious. For example, he claims that the original token/Istream include was completely broken, but that only becomes true when you discard the header include guards and replace them with #pragma once like they did. The various changes are chaotic and difficult to retrace. Why not start as a fork of an existing repo and add changes from there? This pretty much prevents the possibility adopting any of the changes. Why did he have the need to add in a windows-specific regex instead of using the C++11 regex like we already do in OpenFOAM?

I have no clue about the detailed implementation at this moment. But regarding the licensing problem, I see that an issue was opened here and in response licensing was changed to GPL3. Isn't that enough?

Probably - I didn't check all of the issues for their repo. Nonetheless, there may be a desire to have MSVC support, but the rejigged code still has to be readable, must continue to work with other OS's and compilers, needs to be either properly integrated or it should be clear which delta changes should be applied to the upstream OpenFOAM code base.

As an interesting example - take a look at https://github.com/Atizar/RapidCFD-dev/commit/fe0e0ce50c2448bebcba8bd605ff897ea0858703 The number and location of changes is quite impressive, but long-term maintenance will not be much fun.

Sent Amir an email. Let's see what he thinks.

mentioned in issue #2288 (closed)

Additional point: https://github.com/microsoft/Microsoft-MPI/issues/57

Thanks a lot, Mark. IMHO eventually there should be non-MPI binaries released as well. Elmer folks do that too.

what happens if you specify WM_MPLIB=dummy in the prefs.sh (or bashrc) file? I would have thought that this should work.

Do you mean to compile it inside MSYS2 without MPI?

No. All of the OpenFOAM parts are assembled with vendor-independent layer, it is called Pstream. This allows you to recompile those bits (eg, for OPENMPI, INTELMPI, etc) without recompiling the rest of OpenFOAM.

There is always a "dummy" implementation compiled as well. It completes the linkage for OpenFOAM, but it you try to start with it in parallel, it emit a complaint and exit.

You (or someone else) will need to check if it was always shipped, or gets clobbered by the ms-mpi interface. I don't have windows.

seems like an interesting idea. gonna try and let you know.

forget it, I just checked with the packaging - not possible. But I've just made a change to also pack in the dummy version (next release).

mentioned in commit 83243cf0

@foadsf - modified the 'packer' script to include the following:

libPstream.dll-msmpi : the MPI interface with msmpi
libPstream.dll-dummy : a no-op MPI interface. Serial only
libPstream.dll : a copy of the -msmpi or the -dummy version.

@Pawan will see if he can built that into the installer. Eg, if Admin and want MSMPI -> install and use the libPstream.dll-msmpi, otherwise copy the libPstream.dll-dummy on top of libPstream.dll so that it should (hopefully) at least work in serial without Admin rights.

Thanks a lot, Mark, Please let me know when/how I can test this.

Hi Foad,
If you install latest OpenFOAM-v2112 by downloading OpenFOAM-v2112-windows-mingw.exe and install it without admin right, you will be able to run OpenFOAM on single processor without any issue. Let me know if you face any issue. Can you check and let us know whether it work for you. Thanks Pawan

Closing out as solved. Reopen if needed

closed

Native Windows binaries using MSYS2

Child items

Activity

Admin message

Native Windows binaries using MSYS2

Child items

Linked items

Activity