Windows executable standalone problems

Hello, i have developed a GUI program and i used the deploytool to make a windows standalone application (i.e added also the MCR and the then clicked on the package button). When the build was finished, i opened the package on the same machine that I built it and it required to install the Matlab Runtime Compiler that was ~1Gb. After installing, the executable file opened but with a large delay after i double click on it (more than one minute).Is these things normal? What am i doing wrong?

Answer 1

[Image Analyst]

That's normal. The first time it's run it takes longer because it has to unpack a bunch of stuff to separate files, which it won't have to do the second and subsequent times.

[George Lazaridis]

Dear Image Analyst, this seems completely logical but my concern is at the fact that the Matlab Runtime Complier was ~1Gb and that it had to be installed on the same machine that I built my program. So, I have to give to my clients a DVD containing 1Gb of information? What am i missing here?

[Image Analyst]

The R2014a MCRInstaller is 602 MB. I have a bunch of my compiled apps and data and my installer is 84 MB.

I'm not sure why you think you're missing something. You're not missing anything as far as I can tell. You have it correct (except for the size).

[George Lazaridis]

Thanks a lot for taking the time to answer. My final package is 500MB but the MCR installer when being installed is 1Gb as i aforementioned. To sum up, when I want to give the program to someone, i have to burn a CD (not a DVD) with the 500Mb package only? This is my main concern: what do i have to burn.

 P.S: how the 1GB installer will appear? Does it have anything to do with the fact of zip compression or something?

[Image Analyst]

You need to put the 602 MB MCRInstaller.exe and your app's exe (or installer if you used a third party installation building program instead of deploytool, like I do) onto the CD, or DVD or flash drive or shared drive or cloud or whatever storage media you want. It does not have to be strictly a CD only. So you need to ship at least those two files. If your data files, documentation, splash images, or any other files are not included in your app's installer then you should ship those files also. You do not need to ship source code to your end user, but can if you want to, though it's not used by the compiled app.

[George Lazaridis]

Last question: i used the deploytool and i clicked "add mcr to package". Do i still need to put MCRInstaller.exe separately ?

[Image Analyst]

I haven't done that but I would guess not, from the sounds of it. You might want to do it once, but only once if you don't like shipping large files around. Typically I ship them as separate files. They need to install the MCR only once, but my app they typically install several times. You'd be surprised (if it's your first time) how many times your app either doesn't work or the users want some additional feature. It's pretty much expected that when I install the first version on the end user's computer that something won't work 100% correctly. Then you need to modify your app and install it again. I don't want to have them have to install the whole huge MCR all over again when it's already installed, so that's why I keep them separate.

[George Lazaridis]

thank you for your time my friend