Info
此问题已关闭。 请重新打开它进行编辑或回答。
Compiler in 2017b fails to package scripts that compiled well in 2016b
1 次查看(过去 30 天)
显示 更早的评论
After my previous question regarding a compiler problem in 2017a, https://uk.mathworks.com/matlabcentral/answers/355368-compiler-in-2017a-fails-to-package-scripts-that-compiled-well-in-2016b, I have now experienced the same issue using 2017b. Except, it seems to be worse now.
To reiterate, for several years I have used Matlab Compiler via the compiler application to produce a standalone executable from a series of scripts (plus a few images as part of a limited GUI). Up until 2016b, they always compiled into an installer about 10-12 MB in size.
In 2017a, this increased to around 40 MB using precisely the same input - no errors in the packaging log, just this to go on:
![](https://www.mathworks.com/matlabcentral/answers/uploaded_files/170506/image.png)
I installed Matlab 2017b today and fed the same input (scripts and a few images) through the compiler application. They compiled into an installer of 100 MB. Again, no errors in the packaging log, just the same image as above.
What could be causing this?
I'd really like to use the most recent version of Matlab, but until this is resolved I'll have to keep using 2016b, as it's the only way to produce a reasonably sized installer for my standalone program.
All help will be gratefully appreciated.
0 个评论
回答(0 个)
此问题已关闭。
另请参阅
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!