Hello! I’m building the latest develop commit b13a67 with the script
cmake -G "Visual Studio 17 2022"\ -DCMAKE_GENERATOR_PLATFORM=x64 -A x64 -DUSE_SCOTCH=OFF -DUSE_VTK=OFF -DUSE_ELAS=OFF -DCMAKE_WINDOWS_EXPORT_ALL_SYMBOLS=TRUE -DLIBMMG_SHARED=ON -DCMAKE_GENERATOR_TOOLSET="v143" .. set CL=/D_CRT_SECURE_NO_WARNINGS=1 %CL% cmake --build . --config Release
and the linking fails with
even though the function MMG5_chkmesh and so on are clearly present.
No clue what might be the issue here (some CMake hickup?); It might very well not be mmg’s problem but maybe someone here has an idea nevertheless.
On a related note: would it make sense / be interesting to write a hand-curated solution file for building mmg.dll, in addition to the CMake script, just for those cases where invoking CMake might be difficult? If I’m not mistaken, the only difficulty in doing so would be to decide how to process the two files with .in extension in the directory src/common. All other source files could just be compiled as-is into the dll. If it would make sense, I can try to set up a PR. I have the impression that some “CI/CD pipelines” can sometimes look simpler, or at least easier to reproduce, without CMake. What do you think?