MATLAB Compiler vs MATLAB Coder

Question

What's the difference between the two?

As far as I understand it, MATLAB Compiler wraps the MATLAB code into a .exe file so that it can be used without installing MATLAB, and only requires the MCR. On top of it MATLAB Builder NE can also be used to produce .Net assemblies to be used with .Net framework instead of the .exe file, but they still require MCR.

Now I don't understand what MATLAB Coder used for? It generates C/C++ code. But is the MATLAB code really converted into C/C++, or is it merely packaged like in the case of MATLAB Compiler? Does it also need the MCR to run?

I understand that this is not exactly a programming question. But I have searched the internet and still haven't found a clear answer. These are very expensive products so I would like to know what I am getting into.

Thomasson

This question would be a perfect opportunity for users to update and edit the tag wikis for matlab-coder and matlab-compiler. The latter appears to be generic and specific to Matlab itself. – Licentiate

@Licentiate Good point, I have edited the matlab-compiler tag. They are both still a bit concise, but I don't have anything better. – Anisometric

Answer 1

MATLAB Compiler encrypts and archives your MATLAB code (which remains as MATLAB .m code), and packages it in a thin executable (either .exe or .dll) wrapper. This is delivered to the end user along with the MATLAB Compiler Runtime (MCR). If you wish, the MCR can be packaged within the executable as well.

The MCR is freely redistributable, and you can think of it as essentially a copy of MATLAB without a front-end desktop.

When the user runs the executable, it dearchives and decrypts the MATLAB code, and runs it against the MCR instead of MATLAB. Applications delivered via this method should therefore run exactly the same as they do within MATLAB (including the same speed).

MATLAB Coder converts a subset of the MATLAB language into C code. This can then be used in many different ways, including being brought back into MATLAB as a mex file, compiled with a C compiler to be called from another application, or delivered to an embedded device. Since it is C code rather than MATLAB code, it will often (though not always) run much faster than the original MATLAB code. The C code does not require the MCR. The supported subset of the MATLAB language is very extensive, but there are a few notable restrictions that you would want to look into before committing to this workflow. The code produced is C code, although it can produce a C++ wrapper if you have a need to use a C++ compiler rather than a C compiler.

MATLAB Compiler is intended for the use case that you want to simply and (fairly) straightforwardly share a MATLAB application that you've written with someone who does not have a copy of MATLAB. Since the deployed .m code is encrypted, it can also be used to share MATLAB code while protecting intellectual property.

MATLAB Coder has other use cases, such as wanting to speed up MATLAB code by converting to a mex file, or needing to produce C code for another application or an embedded device.

If you have more detailed questions, I would really recommend that you just call up MathWorks and ask them.

---

Edit: The information above is correct for versions of MATLAB R2014b and below. As of MATLAB R2015a, functionality from MATLAB Compiler has been remixed with functionality from the MATLAB Builder products, and there is also a new product MATLAB Compiler SDK.

As of R2015a, MATLAB Compiler works in the same way as described above (i.e. encrypt, archive and package, but not producing C), but will now package as .exe, and as an Excel add-in (.xla). Prior to R2015a, this functionality used to be present in the product MATLAB Builder EX for Excel.

As of R2015a, MATLAB Compiler no longer produces .dll components. This functionality has been moved to the new product MATLAB Compiler SDK, which also includes functionality to produce .NET assemblies and Java classes. Prior to R2015a, this functionality used to be present in the products MATLAB Builder NE for .NET and MATLAB Builder JA for Java.

In other words:

In R2014b and below, we had:

MATLAB Compiler: produce .exe and .dll components

MATLAB Builder NE for .NET: produce .NET assemblies

MATLAB Builder JA for Java: produce Java classes

MATLAB Builder EX for Microsoft Excel: produce Excel add-ins.

In R2015a, we have:

MATLAB Compiler: produce .exe and Excel add-ins

MATLAB Compiler SDK: produce .dll, .NET assemblies and Java classes.

The scope and use-cases of MATLAB Coder have not changed across these releases (although there are new features).

---

Edit: As of R2015b, MATLAB Compiler SDK also produces Python packages.

---

Additional information on distinguishing MATLAB Coder and MATLAB Compiler for C/C++ can be found here.

Comparison table of different MATLAB Products for code generation.

Mic

@Chetan Rawal would you happen to have any information for the new 2016a version? What you have is already enough but I am just wondering if 2016 produced any new information. – Romilda

What is the feedback on the ability to have figures and GUIs compile? – Vendee

@Vendee You can compile GUI applications that use figure windows. – Mic

Answer 2

MATLAB Compiler SDK provides shared libraries that run against a MATLAB Runtime (MCR). It supports most of the features in MATLAB, including graphics, and protects your intellectual property by encrypting your MATLAB code.

MATLAB Coder, on the other hand, provides readable and portable source code. It supports a subset of the MATLAB Language focused on algorithms performing numerical computations.

This MATLAB Answers goes into more details comparing these two approaches:

http://www.mathworks.com/matlabcentral/answers/223937-should-i-use-matlab-compiler-sdk-or-matlab-coder-to-integrate-my-matlab-applications-with-c-c

For example, MATLAB Compiler SDK can be deployed only to platforms that support MATLAB (Windows, Mac, Linux) whereas MATLAB Coder generates C code that can run on any platform that supports C code.

Also, the packaged code from MATLAB Compiler SDK is encrypted to protect IP, whereas the generated C code from MATLAB Coder can be protected in the same way hand written C code is protected.

It's also worth noting that generated C code from MATLAB Coder has the potential of faster execution while the packaged code from MATLAB Compiler SDK will run as fast as it does in MATLAB.

Flatworm

Answer 3

I'm not an expert, but the Coder is described as generating standalone C/C++ code, making no mention of the MCR. I notice however that it says that it only supports a "subset" of the Matlab language, which you can read more about here. The Compiler appears to just package up your Matlab code as you suggested, so probably supports most features.

Donegan

Answer 4

MATLAB coder generates C/C++ code, which could also depend on 3rd party libraries such as intel's TBB/IPP. If you want truly vanilla C/C++ code, you need MATLAB's embedded coder.

On the other hand, MATLAB compiler produces encrypted executables/libraries/etc which runs against MCR (Matlab runtime library). This requires the target computer to pre-install MCR (at no cost). Since MCR is over 1 GB in size, it's not very retargetable.

MATLAB coder is also more expensive than MATLAB compiler.

Subbase

The distinction here between MATLAB Coder and Embedded Coder isn't accurate. When the hardware is set as MATLAB Host in some cases libraries are used. Even without Embedded Coder you can change the hardware settings to get vanilla C or C++. Embedded Coder adds more customizations, optimizations, and verification workflows on top of MATLAB Coder or Simulink Coder. – Marylyn