MATLAB: Shared MCR instance for mixed Matlab deployments (.exe, .jar)

builder jadeploytoolMATLAB CompilerMATLAB Compiler SDKmcrmcr communicationmcr singletonshared mcr

Hi all,

we're currently trying to find a way to exchange data and function calls between two deployed Matlab projects. As for now both executables run in separate MCR instances.

One of the projects is a compiled GUI project (.exe), the other project a Java connector class to the GUI (deployed with Builder JA).

So our first idea was to run those two projects in a shared MCR instance (a MCR singleton). It seems that for Builder NE and JA deployments this is possible, but not for bare .exe or mixed deployments.

So is there a "golden and simple way" to get this communication between this separate deployments working? Maybe in a single MCR instance or by different means (setmcruserdata between instances, …)?

Thanks a lot for any ideas,

Philipp

(Matlab R2009b)

Best Answer

Hi,

There is no "golden and simple way". You have to implement this process communication by your own. Unfortunately MATLAB hasn’t any functionality for that.

Easiest way would be some File I/O (e.g. mat files) to transfer data between the processes.

Related Solutions

MATLAB: Is MinGW compiler supported with MathWorks deployment products like Builder EX, Builder NE etc

MinGW 4.9.2 Compiler is not supported with deployment products like Builder EX and Builder NE.

The Builder products in MATLAB are bundled under the MATLAB Compiler SDK Toolbox. For more information on the supported compilers for these products, refer to the supported compilers page:

https://www.mathworks.com/support/compilers

MATLAB: MCR Shared option in deploytool

According to the documentation,

Shared MCR Instance — When using MATLAB Builder NE, you can create a shared MCR instance, also known as a singleton. The builder creates a single MCR instance for each MATLAB Builder NE component in an application. You can reuse this instance by sharing it among all subsequent class instances within the component. Such sharing results in more efficient memory usage and eliminates the MCR startup cost in each subsequent class instantiation. All class instances share a single MATLAB workspace and share global variables in the MATLAB files used to build the component.

The downside of this is mentioned in a recommendation in a blog:

Don't create or use non-constant static state anywhere (in M, C++ or Java code). Code that uses global variables, for example, will likely yield unexpected results if other applications share the MCR's global resources.

Best Answer

Related Solutions

MATLAB: Is MinGW compiler supported with MathWorks deployment products like Builder EX, Builder NE etc

MATLAB: MCR Shared option in deploytool

Related Question