How to specify MCR version when running executable on Windows (problem with conflicting MCR versions)?

I have a client who has another MCR installed and it is conflicting with the MCR that is required for my deployed application. I am trying to resolve the problem.

Some info online seems to indicate that the deployed application 'should' find the correct runtime, but info here suggests otherwise:

• Your library path may contain multiple versions of MATLAB Runtime. Applications launched without using the shell script use the first version listed in the path. From https://uk.mathworks.com/help/compiler/mcr-path-settings-for-run-time-deployment.html

Please can someone point me to the correct shell command sequence to specify the runtime and the deployed application path?

Note: The deployed application is currently being executed using a Java processbuilder object, that simply includes a path to the executable. It seems straightforward to include additional arguments as if I were just using the Windows command prompt.

Answer 1

[Shan]

On Windows, you can install multiple versions of MCR and the MCR installer automatically sets the path. Manuallly modifying the path or using a shell script to lauch the compiled application is required if the the app is running on Linux or macOS. More details can be found in the following documentation:

• Install Multiple MATLAB Runtime Versions on Single Machine: https://www.mathworks.com/help/compiler/install-the-matlab-runtime.html#bvf5_vk-5
• (see "Note" section) https://www.mathworks.com/help/compiler/magic-square-example-c-c-developer-tasks.html#bs4w1en

Can you elaborate on how the MCRs are "conflicting" on the user's machine? Is the user getting any error messages?

[Daniel Lurcock]

Thank you for your reply. There is no error message, only the Matlab runtime never opens. He has tried changing the order of the runtimes in the Environment Variables list, but that then causes issues with his other software.

As is so often a frustration, I do not have access to his computer and cannot reproduce the issue on my own computer. I appreciate that in theory the executables 'should' pick up the correct runtimes by themselves, but I was wondering if there was a way of calling the exectuables from a shell/bash command and explicitly specifying the runtime that way. Or maybe that's not possible on Windows?

Maybe the problem is because a) we are using quite an old runtime (2011b) or b) there maybe a problem with his runtime installation...?

[Bruno Luong]

Shoting in the dark here but make sure the MCR installation is done with administrator privilege, then restart the PC.

[Daniel Lurcock]

I think this was done, but I will check again. Thanks