Why does mcc generates Warning message about starup file even though the starup file is not present on MATLAB Search Path?

18 views (last 30 days)
I am trying to create standalone application using mcc and getting the Warning message:
[Warning: Your deployed application may error out because file or folder paths
not present in the deployed environment may be included in your MATLAB startup
file. Use the MATLAB function "isdeployed" in your MATLAB startup file to
determine the appropriate execution environment when including file and folder
paths, and recompile your application.
]
I confirmed that there is no starup.m file present on MATLAB search path.
>> which startup.m
'startup.m' not found
 
>>mcc -m myprogram.m -a ./*.mexw64
 

Accepted Answer

MathWorks Support Team
MathWorks Support Team on 1 Nov 2017
You are using -a flag to include certain mexw64 files. This is expected if startup.m exists in same location as mexw64 files.
The issue here is that MCC needs to tell requirements to add the folder to the path when analyzing any of the -a files. We are correctly adding this folder to the path, and the warning was added to better inform the users that the startup.m is being added to the CTF. If you really don't want the startup.m to be added you will need to move it.

More Answers (1)

Jessie Bessel
Jessie Bessel on 4 Jan 2020
Hello! Did you solve the error? I have the same error and I can not figure it out! Can you help me?
  1 Comment
Sam Cook
Sam Cook on 24 Feb 2020
You should be able to safely ignore the message, since it is only a warning. It exists simply to inform users that a startup.m file is added to the compiled archive.

Sign in to comment.

Products


Release

R2017b

Community Treasure Hunt

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

Start Hunting!