How to embed MCR in Matlab Compiler using "mcc"?

Question

Ben 2015-6-30

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/225973-how-to-embed-mcr-in-matlab-compiler-using-mcc

编辑： Will Grant 2016-1-5

I know that using the deploy tool you can select "Add MCR" then "Embed the MCR in the package". However, is there a way to do this using the command "mcc" instead of deploy tool.

Where I work QA likes us to create a sort of "make" file that has the mcc command string. So we can attach it in our configuration management software. So using mcc is preferred over deploy tool.

Thanks for any help!

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Harsheel 2015-7-1

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/225973-how-to-embed-mcr-in-matlab-compiler-using-mcc#answer_184624

Unfortunately, currently there is no way to embed the MCR with the mcc command. The mcc command was designed to be a low-level command like gcc and deploytool was designed to be a high-level command that provided additional capabilities.

1 个评论
显示 -1更早的评论隐藏 -1更早的评论

Ben 2015-7-1

That is what I thought ... but hoped I was just missing it somewhere in the documentation. Not that big of a deal really it just would have been 1 less S/W configuration step.

请先登录，再进行评论。

Answer 2

Will Grant 2016-1-5

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/225973-how-to-embed-mcr-in-matlab-compiler-using-mcc#answer_205170

编辑：Will Grant 2016-1-5

在 MATLAB Online 中打开

I use Bamboo as a build server and currently build our matlab c++ library target using deploytool. Configuration is done in the deploytool gui as normal, then I just call a very simple matlab function containing this code as the build step on Bamboo:

!deploytool -build "path/to/your/deploytool/project/file.prj"

You would probably want to use the -package argument instead of -build. Package will make the installer which should bundle the mcr if you have selected to do so in the deploytool gui. Also, using the ! forces deploytool to be blocking, so execution waits for the library to be built. Useful for our purposes and build system logic.

I know you mentioned your group likes to use mcc, but since the deploytool .prj file is just an xml file describing all the options and files to include it would be simple enough to use this as your point of configuration management. I check the .prj file into our git repo as it's the contents of that file that really decide how the build system runs.

This seems perfectly consistent with using external text-based / repo / whatever build config management your group may want to use.