stand-alone exe's decompose into temp .m's?
4 vues (au cours des 30 derniers jours)
Afficher commentaires plus anciens
Hi-
I have used the Deploy tool to compile a stand-alone exe, but I see that when run, the exe somehow decomposes itself into some constituent .m files in a secret temp folder. This is leading to nstable, unpredictable behavior. I don't know if the temp .m files are depending now on the local DOC command window PATH variable to search for other functions and not finding them... or just that I launch ~64 instances of the exe that are perhaps all sharing that temp folder? Whatever it is, it doesn't work well.
How does all that work... and how do I get a more truly "stand-alone" exe that needs nothing... w/o blowing up the exe size?
Problem has persisted for months :(
0 commentaires
Réponses (1)
Walter Roberson
le 19 Nov 2018
"and how do I get a more truly "stand-alone" exe that needs nothing... w/o blowing up the exe size?"
You would use MATLAB Coder to create the executable. MATLAB Compiler always has the behavior you note.
Voir également
Catégories
En savoir plus sur C Shared Library Integration dans Help Center et File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!