Windows executable standalone problems

1 view (last 30 days)
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?

Accepted Answer

Image Analyst
Image Analyst on 17 Jul 2014
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.
  7 Comments
Image Analyst
Image Analyst on 17 Jul 2014
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
George Lazaridis on 18 Jul 2014
thank you for your time my friend

Sign in to comment.

More Answers (0)

Categories

Find more on Introduction to Installation and Licensing in Help Center and File Exchange

Products

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!