Calling MATLAB scripts from a MATLAB standalone executable

1 ビュー (過去 30 日間)
Souparna Satpati
Souparna Satpati 2022 年 6 月 23 日
コメント済み: dpb 2022 年 6 月 24 日
We have designed a large MATLAB standalone executable and we want it to call external .m scripts without them being compiled while creating the executables. The reason we want to do that is to have the flexibilty to make changes in the .m script and not having to compile them everytime. Is it possible to do that?

回答 (2 件)

dpb 2022 年 6 月 23 日
Not directly supported, no.
I've not tried building one that uses it, but seems like you should be able to use feval with a dynamic function handle/name that is the name of the function to execute.
  1 件のコメント
dpb 2022 年 6 月 24 日
What works during development testing doesn't necessarily translate to compiled version per @Steven Lord's Answer below...and the only warning given is that one doesn't normally need to use feval -- of course, the suggestion to fix hardcodes in the given function so back to same place.


Steven Lord
Steven Lord 2022 年 6 月 23 日
From the documentation "MATLAB Runtime only works on MATLAB code that was encrypted when the deployable archive was built. Any function or process that dynamically generates new MATLAB code will not work against MATLAB Runtime."
  1 件のコメント
dpb 2022 年 6 月 24 日
Ah...I knew the interactive test wsn't totally conclusive -- but didn't want to take the time to actually build a compiled version. Shoulda' done, just to be certain what worked interactively would still work when compiled.
I did see a post to similar Q? that indicated one could load text and eval it...but I didn't test that, either.


Community Treasure Hunt

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

Start Hunting!

Translated by