From: Dan Tyndall on
Hi everyone,

I'm having a bit of trouble with the MATLAB compiler on Windows 7. My code works in the MATLAB environment; however, when I run it using the MCR, it crashes. I've written my code so that outputs an extremely detailed log file, and the code seems to fail when it attempts to call a it's first command from the mapping toolbox--in this case, axesm. Like I said, when I launch the gui from MATLAB itself, the code runs completely fine. Any ideas on what could be causing this? I'm using MATLAB 2009b. Thanks,

-Dan Tyndall
From: ImageAnalyst on
Dan:
1. Have you run Dependency Walker (Google it) on it?

2. Do you check for existence of all files you plan on reading at run
time? Such as splash images, initialization files, etc. Use the
"exist()" function in your code before you try to read in any files!

3. Have you examined the excluded files log to see if any files were
not able to be included in your executable?

4. Have you tried to run the executable from the MATLAB command window
with the ! operator?

5. Have you tried to run it from an operating system command window
(Start/rum/cmd in Windows)?

6. Do you have any subdirectories of your app that you expect to be in
the same folder as your executable? They must be bundled in with
Deploytool, or else some other tricky methods (like I use, but don't
want to get into explaining).

7. Have you searched this newsgroup for other ideas, since this issue
comes up all the time?

8. Does your user have the same version of the MCR that you used to
compile with? Often you distribute a new executable and forgot that
your user was still using the version of the MCR from your old app,
before you upgraded. That won't work. The versions need to match.

9. Have you called the Mathworks for help?

Good luck,
ImageAnalyst
From: Dan Tyndall on
ImageAnalyst,

Thanks you so much for the questions you had asked me in your response! I went through each one, and the one that I found the most helpful was running the executable in the MATLAB command window. I actually had no idea I could do that, and it helped me to figure out that the problem was a missing dependency. I had originally thought that MATLAB would package in all of the routines needed by the program in the MATLAB compiler, but for some reason, it excluded the mapping toolbox, which I need because I use map plot commands, and not just the normal plot.

As far as searching the forum first, I actually had searched for the problem, but the problem was related to the fact that I thought it was a combined problem with the mapping toolbox and MATLAB compiler (so I believe I was searching for something like, "compiler mapping toolbox," which didn't return many results.

Thanks again for all of your help.

-Dan