MATLAB R2025b Compiler mcc Parameters

MATLAB R2025 (I'm using b) has dramatically changed the Compiler format and I'm having trouble finding equivalent functionality to previous versions. Previously, in "Settings" there would be a field for "Additional parameters passed to mcc". I had found that the following was required for applications that used Instrument Control Support Packages (e.g., Keysight):

-a C:\ProgramData\MATLAB\SupportPackages\R2024b\toolbox\instrument\supportpackages\keysight

I cannot find a similar functionality in the R2025 Compiler GUI. Am I missing something somewhere? Do I for some reason no longer need to include this? Just trying to make sure that my applications will continue to run after migrating to R2025b.

Answer 1

[dpb]

The <Additional Files> switch is still available to the mcc compiler; for some totally unfathomable reason, <this Mathworks Staff link> says it was left out of the GUI inteface by design. How in the world could have come to that decision is truly mind boggling.

First thing would be to just try to compile as is; it'll let you know if it can't find something needed on linking. I'd suspect that will be the case without the additional library unless there's somewhere else a checkbox about the needed external library.

[Brian]

The thing is in my particular instance, it identifies that the Instrument Control Toolbox Support Package for IVI and VXIplug&play Drivers is identified as a required support package, but the Instrument Control Toolbox Support Package for Keysight IO Libraries and VISA Interface is not. I was previously able to use the -a command to force it to add that package, but with the new "everything has to be in the project folder" format, I can no longer add the Support Package folder because it gets installed in the ProgramData folder. I guess this falls under the "PLEASE FIX IF YOU WANT ME TO EVER USE THIS PRODUCT" category...

[dpb]

Will the <options> object let you specify the needed location?

Submit this to Mathwor ks as an official support ticket item at <Product Support Page>. It seems there ought to be something addressed in the IC TB doc on the subject.

[Brian]

It seems like it should. This does let you export the build script, and I feel like I could probably just add the additional support package in buildOpts.SupportPackages that way. But I dislike workarounds. Ideal performance (in my opinion) would be to list all of the available Support Packages and automatically select the required packages that are auto-detected.

[dpb]

No argument whatsoever on the fact the reworked interface and requirement for projects has been a major regression, at least initially. If one doesn't formally complain and get these issues and suggested improvements, however, the chances of specific issues getting picked up and in the official bug/enhancement database(s) are minimal; even if a Mathworks staffer sees this, it's not guranteed they will go the extra mile.

[Brian]

Gross... Turns out that the Instrument Control Toolbox Support Package for Keysight IO Libraries and VISA Interface is not a deployable support package, but it looks like I can specify the support package folder under the AdditionalFiles argument, which then passes the same -a argument to the mcc call. This just doesn't work in the GUI because the GUI for some reason requires additional folders/files to be within the project root (defaulting to and seemingly unchangeable from the MATLAB root folder) and the support packages are in the ProgramData folder.

[Image Analyst]

Applets inside MATLAB that have their own little GUI have never been allowed to be included in a standalone executable. For example, your compiled program cannot call any of the applets on the Apps tab of the tool ribbon.d

I use the -a option in a script I have that compiles my programs and does a few other things, but it has to be something that can be included.

[Brian]

Understand that I can't include applets, but if I am interfacing with a piece of Keysight hardware via VISA from a deployed application, I need the support package, but it isn't a deployable support package. Is this a failure in how I have implemented something, or a failure in how MATLAB has implemented something?

[dpb]

I think the only definitive answer to this question is to ask Mathworks as an official support request at <Product Support Page>.