compiler.r​untime.cus​tomInstall​er fails to reduce mcr installer size

10 次查看（过去 30 天）
Sadiya
Sadiya 2024-10-29
编辑： Sadiya 2024-10-30
I have a matlab toolbox, with a single-window GUI. I was able to build it mcc/deploytool to create a standalone 7MB executable. However, I was not happy for the installer size, as the R2016 matlab runtime is 700MB in size, 100x larger than my application.
When I saw a new matlab compiler API compiler.runtime.custominstaller coming with R2024b is cable of creating smaller MCR installer including only needed files, I was very happy and immediately tried it on free mod apk games website, however, the result was disappointing.
The installer bundled with MCR in R2024b for my app build by deploytool - without using the customInstaller - is 1.2GB in size (another 2x increase in size compared to the already large package generated by R2016). Then, when I called
results = compiler.build.standaloneApplication("myapp.m");
compiler.runtime.customInstaller("myapp_installer", results, 'RuntimeDelivery', 'installer');
however, the generated package has the same 1.2GB in size. I have followed the help page of compiler.runtime.customInstaller
https://www.mathworks.com/help/compiler/compiler.runtime.custominstaller.html
did I miss anything? why customInstaller fails to trim the installer size? my app only use basic matlab features.
the requiredMCRProducts.txt file shows that I only need the following MCR components
  • 'MATLAB Runtime - Core'
  • 'MATLAB Runtime - Graphics'
  • 'MATLAB Runtime - Non Interactive MATLAB'
  • 'MATLAB Runtime - Numerics'
  • 'MATLAB Runtime - Image Processing Toolbox Addin'

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

回答（2 个）

Rik
Rik 2024-10-29
I don't know why the size doesn't decrease when using the new function. Do you only have these toolboxes installed? If so 'required' and 'all' wouldn't be different.
The point is that the MCR is essentially a full copy of Matlab. Your function might be 7MB, but running it requires Matlab. If you want to decrease the size, you need to convert your code to C or C++. This is not possible with all functions (and it requires the compiler toolbox).
Sumukh
Sumukh 2024-10-30
Hi Sadiya,
The command “compiler.runtime.customInstaller” creates an installer that installs the MATLAB Runtime components required by the toolbox, and not the complete MATLAB Runtime. The installer has minimal footprint by default as it installs the MATLAB Runtime components from the MathWorks® website during application installation. This is specified by the “RuntimeDelivery” name-value argument that is set to “web” by default. You can refer to the following documentation to know more about this argument:
https://www.mathworks.com/help/compiler/compiler.runtime.custominstaller.html#mw_16cb3557-b675-43e7-8bee-1a670b8b2e92
The installer includes the MATLAB Runtime components within the installer if the “RuntimeDelivery” option is set to “installer”. This increases the size of the installer. The total size of the MCR components specified in the “requiredMCRProducts.txt” file is close to 1.2GB. This can be verified from the installation dialog box when using the “web” installer to install the Runtime components. The size of the MATLAB Runtime components has significantly increased owing to the addition of features release after release since MATLAB R2016a.
You can set the “RuntimeDelivery” option to “web” to have a much smaller installer size (1.9MB). The installer automatically installs the necessary MATLAB Runtime components for the toolbox from the internet wherever the installer is executed.

类别

在 Help Center 和 File Exchange 中查找有关 Introduction to Installation and Licensing 的更多信息

标签

产品

Community Treasure Hunt

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

Start Hunting!

Translated by