Problems with meshmonk when installing on ARM64 architecture (M1 chip°

[PieterJanVe]

Hi there,

I recently needed to reinstall Meshmonk again on my new M1 macbook. I now get an issue in matlab when I want to run meshmonk, concerning the libmeshmonk.dylib architecture:

MException with properties:

identifier: 'MATLAB:mex:ErrInvalidMEXFile'
   message: 'Invalid MEX-file '/Users/pieter-janverhelst/Documents/MATLAB/ImgGENESoftware/myCompiledToolboxes/compute_correspondences.mexmaci64': dlopen(/Users/pieter-janverhelst/Documents/MATLAB/ImgGENESoftware/myCompiledToolboxes/compute_correspondences.mexmaci64, 0x0006): Library not loaded: libmeshmonk.dylib↵  Referenced from: /Users/pieter-janverhelst/Documents/MATLAB/ImgGENESoftware/myCompiledToolboxes/compute_correspondences.mexmaci64↵  Reason: tried: '/Applications/MATLAB_R2021b.app/bin/maci64/libmeshmonk.dylib' (no such file), '/Applications/MATLAB_R2021b.app/bin/maci64/./libmeshmonk.dylib' (no such file), '/Applications/MATLAB_R2021b.app/bin/maci64/../../sys/os/maci64/libmeshmonk.dylib' (no such file), '/Applications/MATLAB_R2021b.app/Contents/MacOS/libmeshmonk.dylib' (no such file), '/Applications/MATLAB_R2021b.app/Contents/MacOS/./libmeshmonk.dylib' (no such file), '/Applications/MATLAB_R2021b.app/Contents/MacOS/../../standalone/bin/maci64/libmeshmonk.dylib' (no such file), '/Applications/MATLAB_R2021b.app/Contents/MacOS/../../sys/os/maci64/libmeshmonk.dylib' (no such file), '/Applications/MATLAB_R2021b.app/Contents/MacOS/../../bin/maci64/libmeshmonk.dylib' (no such file), 'libmeshmonk.dylib' (no such file), '/usr/local/lib/libmeshmonk.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')), '/usr/lib/libmeshmonk.dylib' (no such file), '/Users/pieter-janverhelst/Desktop/VECTRA/IMAGES/libmeshmonk.dylib' (no such file), '/usr/local/lib/libmeshmonk.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')), '/usr/lib/libmeshmonk.dylib' (no such file)'
     cause: {}
     stack: [2×1 struct]
Correction: []

Seems to be a compatibility issue between the X86_64 design and the new arm64 architecture. Is this a known issue and are there any solutions? Thanks in advance!