Not sure if I messed something up but it seems to me that after building the “INSTALL” target that cmake automatically generates, the global file mmg_export.h in the folder “mmg\include\mmg” also expects a global mmgcmakedefines.h:
but there are only three such files in the subordinate folders mmg2d, mmg3d, and mmgs, not a global one. Maybe CMake should also manufacture such a global “mmgcmakedefines.h”.
However: If I can tell correctly, there is nothing so complex in the build process of mmg that absolutely requires CMake and can’t be done directly with a project file and Makefile. Personally I think it would be better to hand-write a Visual Studio project file for Windows, and a Makefile for Linux, and getting rid of CMake altogether but who am I to say …