As I recall, the package .exe contains both MCR.exe (because you chose to add it) and the application .exe . When you execute the package .exe, it will unpack both of these.
When I deploy the compiler, I place my program as the "main file" in the build tab. Then in the package tab, i say "Add MCR". once the build is complete, a folder is created with the name of my program. Inside that folder, there are two folders. One is called "distrb" which has a readme file and the .exe file for my program. The other folder is called "src" and contains another .exe file for my program, two .txt files and three C Source files. There is no other .exe file. I'm guessing i'm doing something wrong.
> When I deploy the compiler, I place my program as the "main file" in the build tab. Then in the package tab, i say "Add MCR". once the build is complete, a folder is created with the name of my program. Inside that folder, there are two folders. One is called "distrb" which has a readme file and the .exe file for my program. The other folder is called "src" and contains another .exe file for my program, two .txt files and three C Source files. There is no other .exe file. I'm guessing i'm doing something wrong.
=================
How big is the .exe in distrib and what happens when you execute it?
> When I deploy the compiler, I place my program as the "main file" in the build tab. Then in the package tab, i say "Add MCR". once the build is complete, a folder is created with the name of my program. Inside that folder, there are two folders. One is called "distrb" which has a readme file and the .exe file for my program. The other folder is called "src" and contains another .exe file for my program, two .txt files and three C Source files. There is no other .exe file. I'm guessing i'm doing something wrong.
==============
After you run the build, you need to run a packaging step, as explained here
http://www.kxcad.net/cae_MATLAB/toolbox/compiler/bqrw9k_-1.html
Either use the menu option Tools > Package or use the package icon. The packaging step will create a self-extracting executable containing the MCR.
Yea thats what i was doing wrong. I went back and looked up some demo's again...i missed the packaging part last time i watched the demo. Thanks anyway.