Borrar filtros
Borrar filtros

How to bypass startup file in Application Builder

2 visualizaciones (últimos 30 días)
John F
John F el 24 de Feb. de 2017
Comentada: John F el 28 de Feb. de 2017
I am trying to build a standalone app. I have been successful in the past doing it. However, I now have a custom startup.m file that includes calling Simulink and other commands. When I try to run the deployed apps I'm building, they all try to start Simulink, and thus they crash.
I know there must be a way to bypass these commands, but I can't seem to find it in the Documentation. Please help!

Respuesta aceptada

Faiz Gouri
Faiz Gouri el 27 de Feb. de 2017
The startup.m file is always included with the compiled application. This is to ensure that the behavior of MATLAB and the compiled application is same during the initialization phase. If you want some statements in the startup.m file to NOT execute when the compiled application is running then, wrap those statements under isdeployed .
if (~isdeployed)
% code that calls Simulink and other commands
end
For information about "isdeployed" can be found here

Más respuestas (0)

Categorías

Más información sobre Multicore Processor Targets en Help Center y File Exchange.

Productos

Community Treasure Hunt

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

Start Hunting!

Translated by