mpich | Official MPICH Repository | Performance Testing library

Use CMAKE_PREFIX_PATH variable to set search path. Best practice is set that variable in command line interface:

I've outlined all the required fixes (including the DBL_MAX fix) here: https://github.com/Repast/repast.hpc/issues/7. With those in place, the zombies and rumor demo models work on macOS on an M1 Max laptop.

All that said, and as an aside, we typically do our repast hpc and repast4py development work on a Linux VM running under Parallels or VMWare Fusion on a Mac. This is because that more closely matches the cluster or HPC environments we ultimately run the models on.

Try this:

Setting -DMPI_ROOT= or -DMPI_HOME= didn't work for me. It still uses the default in my system (OpenMPI).

What worked was to set -DMPI_EXECUTABLE_SUFFIX=.mpich, option which I found near the end of the documentation: https://cmake.org/cmake/help/latest/module/FindMPI.html.

I found the solution: I got to run source /etc/profile with fabric in order to get my correct PATHs.

Found out by reading: https://www.gnu.org/software/bash/manual/bash.html#Bash-Startup-Files

I can't answer but maybe I can orient you.

First nmake is not make. It will not work with any makefile not written specifically as an nmake makefile. And it's only available on Windows. So, best to just forget it exists.

Second, it's important to understand how make works: rules in makefiles are a combination of targets/prerequisites, and a recipe. The recipe is not in "makefile" syntax, it's a shell script (batch file). So make works in tandem with the shell, to run commands. Which shell? On POSIX systems like GNU/Linux and MacOS it's very simple: a POSIX shell; by default /bin/sh.

On Windows systems it's much less simple: there are a lot of options. It could be cmd.exe. It could be PowerShell. It could be a POSIX shell, that was installed by the user. Which one is chosen by default, depends on how your version of make was compiled. That's why you see different behaviors for different "ports" of make to Windows.

So, if you look at the makefiles you are trying to use you can see they are unquestionably written specifically for a POSIX system and expect a POSIX shell and a POSIX environment. Any attempt to use a version of make that invokes cmd.exe as its default shell will fail immediately with syntax errors ("" was unexpected at this time.).

OK, so you find a version of make that invokes a POSIX shell, and you don't get that error anymore.

But then you have to contend with another difference: directory separators. In Windows they use backslash. In POSIX systems, they use forward slash and backslash is an escape character (so it's not just passed through the shell untouched). If you are going to use paths in a POSIX shell, you need to make sure your paths use forward slashes else the shell will remove them as escape characters. Luckily, most Windows programs accept forward slashes as well as backslashes as directory separators (but not all: for example cmd.exe built-in tools do not).

Then you have to contend with the Windows abomination known as drive letters. This is highly problematic for make because to make, the : character is special in various places. So when make sees a line like C:/foo:C:/bar its parser will get confused, and you get errors. Some versions of make compiled for Windows enable a heuristic which tries to see if a path looks like a drive letter or not. Some just assume POSIX-style paths. They can also be a problem for the POSIX shell: many POSIX environments on Windows map drive letters to standard POSIX paths, so C:\foo is written as /c/foo or /mnt/c/foo or something else. If you are adding paths to your makefile you need to figure out what the right mapping, if any, is and use that.

That's not even to start discussing the other differences between POSIX and Windows... there are so many.

From what you've shown above, this project was not written with any sort of portability to Windows in mind. Given the complexity of this, that's not surprising: it takes a huge amount of work. So you have these options that I can see:

1. Port it yourself to be Windows-compatible
2. Try to get it working inside cygwin (cygwin is intended to be a POSIX-style environment that runs on Windows)
3. Try to get it working in WSL
4. Install a virtual machine using VMWare, VirtualBox, etc. running a Linux distribution and build and run it there

Unfortunately I don't know much about the pros and cons of these approaches so I can't advise you as to the best course.

The route I chose, long long ago, was to get rid of Windows entirely and just use GNU/Linux. But of course that won't be possible for everyone :).

The "user" keyword can be used to assign logical cores manually. Hence, one can write:

Seemed to have been a bug, I just saw it was fixed by FreeBSD folks.

See https://cgit.freebsd.org/ports/commit/?id=fd490a171c3da0d7bcb9a5f3ee3b4b46075dfa9e

@VictorEijkhout suggested the following solution in his comments. The idea is to create a communicator object which calls MPI_Init and MPI_Finalize in its constructor and destructor, then pass that object to other functions or classes for further manipulation.