Executable created in Matlab2016 doesn't open up

Hi,

I have executable that made in previous matlab version and now I after making few updates in the code I've tried to regenerate it with help of deplytool in Matlab2016 (Compiler runtime v91). It all goes fine with creating .exe but when I try to lunch it, I just get pop up like it was about to open and a second later it disappears and nothing happens. Any idea what the problem could be?

[Rik]

Just to confirm: you are sure there are no errors? Because it will close without further message if it encounters any.

[Szymon Karabela]

I don't get any errors, unless they're logged somwhere in the background. I'd like to feed you with some info is there any way to catch some usefull diagnostic data?

[Szymon Karabela]

Well, I did recreate .exe with deplytool and in Command Window I get a warning complaining baout M-code missing in the folder. This seems to be the reason why it goes wrong, how to fix it?

>> deploytool Warning: Requirements cannot analyze C:\Users\scarabel\AppData\Roaming\MathWorks\MATLAB\ModulesCache\F3D67FBD7F196695\R2017_07_19\Basics\toolbox\matlab\iofun\set_web_credentials.p unless the user provides a corresponding M-code along with it in the same folder. Its dependencies may not be included in the completion because its corresponding M-code found by REQUIREMENTS either is empty or contains nothing but comments. > In matlab.depfun.internal.MatlabSymbol/findCorrespondentMCode (line 1157) In matlab.depfun.internal.Completion/recordDependency (line 818) In matlab.depfun.internal.Completion>@(client,symbol)recordDependency(obj,client,symbol) In matlab.depfun.internal.MwFileInspector/recordDependency (line 116) In matlab.depfun.internal.MwFileInspector/evaluateSymbols (line 324) In matlab.depfun.internal.MwFileInspector/analyzeSymbol (line 34) In matlab.depfun.internal.Completion/findDependentFiles (line 1349) In matlab.depfun.internal.Completion/computeDependencies (line 263) In matlab.depfun.internal.Completion/computePartsList (line 2012) In matlab.depfun.internal.Completion/requirements (line 2412) In matlab.depfun.internal.requirements (line 215)

[Szymon Karabela]

I found the post with similar problem, apparently it's problem with P file dependencies with one of the requiered files. Unfortunately - no workaround found yet.

I found the post with similar problem, apparently it's problem wi <https://nl.mathworks.com/matlabcentral/answers/269099-p-files-cannot-be-analyzed-to-find-their-dependencies-please-add-p-file-dependencies-manually P files cannot be analyzed to find their dependencies. Please add P file dependencies manually th P file dependencies with one of the requiered files. Unfortunately - no workaround found yet.>

Answer 1

[Szymon Karabela]

Well, I did recreate .exe with deplytool and in Command Window I get a warning complaining baout M-code missing in the folder. This seems to be the reason why it goes wrong, how to fix it?

>> deploytool Warning: Requirements cannot analyze C:\Users\scarabel\AppData\Roaming\MathWorks\MATLAB\ModulesCache\F3D67FBD7F196695\R2017_07_19\Basics\toolbox\matlab\iofun\set_web_credentials.p unless the user provides a corresponding M-code along with it in the same folder. Its dependencies may not be included in the completion because its corresponding M-code found by REQUIREMENTS either is empty or contains nothing but comments. > In matlab.depfun.internal.MatlabSymbol/findCorrespondentMCode (line 1157) In matlab.depfun.internal.Completion/recordDependency (line 818) In matlab.depfun.internal.Completion>@(client,symbol)recordDependency(obj,client,symbol) In matlab.depfun.internal.MwFileInspector/recordDependency (line 116) In matlab.depfun.internal.MwFileInspector/evaluateSymbols (line 324) In matlab.depfun.internal.MwFileInspector/analyzeSymbol (line 34) In matlab.depfun.internal.Completion/findDependentFiles (line 1349) In matlab.depfun.internal.Completion/computeDependencies (line 263) In matlab.depfun.internal.Completion/computePartsList (line 2012) In matlab.depfun.internal.Completion/requirements (line 2412) In matlab.depfun.internal.requirements (line 215)