Hi Konstantinos,
I understand that you're facing a common challenge with MATLAB version compatibility, especially when trying to use a C++ MEX function you made in MATLAB 2021a and then running it in MATLAB 2023a. The issues is MATLAB does not guarantee binary compatibility for MEX files or applications across major releases. This absence of guaranteed compatibility means that a MEX function compiled with a specific version of MATLAB, such as MATLAB 2021a, might not function as expected—or at all—when executed in a subsequent version like MATLAB 2023a. The root of the issue often lies in changes to MATLAB's internal APIs or the binary interfaces of essential libraries, such as libMatlabEngine.so, that can vary between releases. You can refer to below documents where it is mentioned about version compatibility of mex files.
To address this issue, the first recommended solution is to compile version-specific C++ MEX functions for each MATLAB release intended for support. This approach ensures that each MEX function is linked against the appropriate version of libMatlabEngine.so and other critical MATLAB libraries.
Furthermore, careful management of environment variables, particularly on Linux systems where LD_LIBRARY_PATH plays a crucial role, is essential for ensuring that MEX functions dynamically link to the correct version of MATLAB libraries at runtime. Properly setting these environment variables to point to the specific MATLAB version's library paths can mitigate issues where a MEX function attempts to link to an incompatible version of a library like libMatlabEngine.so .
You can refer to below links for the clear understanding of libraries and version compatibility issues mentioned above.
https://in.mathworks.com/help/matlab/matlab_external/set-run-time-library-path-on-linux-systems.html
Hope this helps!
