Need to compile my matlab code into a standalone executable to run on a 32-bit machine

I have a set of matlab scripts, initiated from a main routine that I need to compile into a stand alone executable that I need to run on a 32-bit machine. The last time our team did this we were using matlab ver 2015b. However the oldest matlab version at our disposal that we are currently running is MATLAB Version: 9.6.0.1072779 (R2019a).

My question for the community is two fold:

1. I would like the step by step instructions of how I go about compiling my code into a stand alone execuatble, as this is my first experience at doing this.
2. Is my current understanding, that I need a matlab version older than what we have 2019a to create a 32-bit executable, correct? If so how can I get around this?

Thank you

Bill Z

Answer 1

[dpb]

R2015b is the last 32-bt version of MATLAB. With a current license, you can install any prior release in parallel with the presently installed release. I did not check whether available releases at the license center go back as far as R2015b or not; if not, you'll have to contact sales directly about getting the older release.

As for how to compile when you do get that far along, you use the mcc compiler product so you'll also need the license for it and the compatible release for R2015b. With R2015b, the GUI development was GUIDE, appdesigner wasn't introduced until R2016a.

[Walter Roberson]

The old versions of MATLAB that can (often) be downloaded, do extend back to R2015b.

[dpb]

Thanks for checking, Walter...

[William]

Thank you for the response. I was able to get matlab 2015b installed and get my applcation compiled.

Answer 2

[Image Analyst]

I can help. I compile programs all the time. I use scripts to call mcc along with a bunch of other stuff to compile my m-files into standalone executables. Tell me the name of your source code folder, and the name of an output folder where you want to store the executable. In addition, tell me all the files you need to ship with your program like .mat files, spreadsheets, text files, data files, artwork or splash images, etc. For example, I also install a text file showing all the changes I made in the versions so far. In addition, I create a file that is names after the version of MATLAB I compiled it with so if someone looks at the program folder, they will be able to see what version of the MATLAB runtime library they need to download and install. You can include the runtime library in your installation but it makes your installer huge. So I have them install it separately then I can give updates of my program in installers that are small.

[Image Analyst]

Also, I use an installation package builder called Centurion Setup to package my MATLAB executable and all the other files needed to complete the entire software suite. It's way better than trying to package everything with the primitive deploytool of MATLAB. Gammadyne Centurion Setup

[dpb]

Thanks for the link to the packaging app, @IA; I had looked some before but had not found this one that looks quite good at reasonable cost. Indeed, the builtin is excruciatingy feeble in its flexibility and quite frustrating to use.