MATLAB Compiler    

Compiler Licensing Changes

Starting with Compiler 1.2.1, a new licensing scheme has been employed that enables the product to be simpler and more user friendly.

In versions prior to 1.2.1, you could not run the MATLAB Compiler unless you were running MATLAB. On networked systems, this meant that one user would be holding the license for one copy of MATLAB and the Compiler, simultaneously. In effect, one user required both products and tied up both licenses until the user exited MATLAB. Although you can still run the Compiler from within MATLAB, it is not required. One user could be running the Compiler while another user could be using MATLAB.

The licensing model is based on how you run the Compiler:

Running Compiler from MATLAB

When you run the Compiler from "inside" of MATLAB, that is, you run mcc from the MATLAB command prompt, you hold the Compiler license as long as MATLAB remains open. To give up the Compiler license, exit MATLAB.

Running Compiler from DOS/UNIX Shell

If you run the Compiler from a DOS or UNIX shell, you are running from "outside" of MATLAB. In this case, the Compiler

Each time a user requests the Compiler, the user begins a 30 minute time period as the sole owner of the Compiler license. Anytime during the 30 minute segment, if the same user requests the Compiler, the user gets a new 30 minute allotment. When the 30-minute time interval has elapsed, if a different user requests the Compiler, the new user gets the next 30 minute interval.

When a user requests the Compiler and a license is not available, the user receives the message

This message is given when no licenses are available. As long as licenses are available, the user gets the license and no message is displayed. The best way to guarantee that all MATLAB Compiler users have constant access to the Compiler is to have an adequate supply of licenses for your users.


  MATLAB Compiler 2.3 Uses of the Compiler