Warnings while compiling in MATLAB 2023b

16 views (last 30 days)
Hello Team
I have been receiving the following warnings when I compile in MATLAB 2023b:
"Warning: Excluded "C:/Program Files/MATLAB/R2023b/toolbox/matlab/codetools/+matlab/+codetools/requiredFilesAndProducts.m"; reason: The file or function is non-deployable and has been excluded from packaging. Either remove the file or function from your code, or use the MATLAB function "isdeployed" to ensure the function is not invoked in the deployed component. Then you can suppress this warning by using the %#exclude pragma. "
"Warning: Excluded "C:/Program Files/MATLAB/R2023b/toolbox/matlab/codetools/+matlab/+desktop/+editor/getActive.m"; reason: The file or function is non-deployable and has been excluded from packaging. Either remove the file or function from your code, or use the MATLAB function "isdeployed" to ensure the function is not invoked in the deployed component. Then you can suppress this warning by using the %#exclude pragma. "
and many more...
1) Will these warnings somehow impact building my exe using MATLAB Compiler? These warnings were not visible in previous versions of MATLAB.
2) How do I find where these files are being called since I am not using them explicitly.

Answers (1)

sai charan sampara
sai charan sampara on 16 Oct 2023
Hello Rajiv,
I understand that you are trying to figure out why the warnings provided in the question are being generated in MATLAB.
These warnings are shown because MATLAB Compiler does not support the deployment of all built-in functions. If a user invokes an unsupported function in a deployed application, the application will not work as expected. Starting MATLAB R2017a, MATLAB added a feature to warn users if they are using an unsupported function in their deployed application. Please ensure that you are not using any unsupported functions or Toolbox functionality in your deployed application.
To understand where these files are being called in the program you can add break points and run the code line by line using step option. Step option helps to execute the code one line after the other and helps in debugging. This can be used to identify the line or the command at which the warning is being generated. Debugging in this way can help identify where the files are being called.
You can refer to a similar question that has been posted and resolved by the MathWorks Support Team:
You can refer to the below documentation to learn more about using breakpoints to debug:
Hope this helps.
Thanks,
Charan.

Categories

Find more on MATLAB Compiler in Help Center and File Exchange

Products


Release

R2023b

Community Treasure Hunt

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

Start Hunting!