With respect to #114, it should be reconsidered which of that is really important. Probably the most important is use of configure or cmake.

/cc @alkichigin

Another potential issue is related to using Fortran on MacOS. Currently, gcc from Homebrew includes gfortran but the gcc itself remains a symlink to clang. This is good for performance, but using clang as a linker ignores gcc standard folders (where gfortran libraries are located).

Thus, we may need to locate this folder (for a specific gcc version) inside Homebrew and specify it during compilation, like

make ... FORT_LIB_PATH=/opt/homebrew/Cellar/gcc/11.2.0/lib/gcc/11

but the path should be built from some internal Homebrew parameters.

Potentially relevant issue is Homebrew/homebrew-core#84245

Concerning different adda modes (seq, mpi, ocl) with different dependences. The preliminary idea is to have following packages (a -> b means a depends on b):

• adda -> gcc, (gfortran), fftw
• adda-mpi -> adda-seq, openmpi (or mpich)
• adda-ocl -> adda-seq, clfft
• adda-all -> adda, adda-mpi, adda-ocl

adda will also compile most of tools in misc/, while adda-mpi - tools in misc/near_field.

But it is still worth studying the examples of other packages, where different modes are used.

This is also related with Continuous Integration (CI) on GitHub. Probably the latter can be implemented independently, but it would be much easier if the packages are already available.

While a comprehensive solution of this issue is non-trivial some partly solutions (e.g., seq version for Unix) is much easier. This can be straightforwardly implemented (together with git clone ...) in other codes that depend on ADDA. See, e.g., https://gitlab.com/k.czajkowski/addatmatrix/ . Potentially, some of such codes can further be used as a base for comprehensive solution.

Another workaround is employed by ADDA GUI - https://github.com/adda-team/adda-gui, but it is not fully automated.