Hi Susannah,
The source codes don't support Mac OS at this moment.
There are a few reasons for this:
1) The code would have to be rigorously tested on different versions of Mac OS that are not backwards/forward compatible - this itself could take a long time. Every single build now takes about 24 hours to validate on a high-end cluster.
2) I don't have a Mac to test the code on (To support different version of Mac OS, I'd need multiple computers with MacOS 10.6-10.10).
3) We would need additional commercial licenses of Intel compiler to create builds for Mac (one per MacOs version). The price for Intel compiler is now $1599 per computer, per year. Unfortunately, we are not allowed to distribute builds with GNU C++ and FFTW since the licenses are not compatible.
However, compilation with GNU C++ and FFTW is not supposed to be so difficult. There are a few differences in memory allocation that I've already overcome I hope.
What needs to be changed by you, is to go over the code and find __linux__ preprocessor directive and create a code path for __APPLE__ which may but also may not be the same. In any case, these compiler/OS specific code paths serve for getting system information (number of cpu cores, memory used, consumed time, and other reports).
If this is not critical for you, I'm more than happy to lend you a helping hand to make the code running on MacOS, just send me an email.
Cheers!
Jiri