| Version 4.1.1 (R14SP1+) MATLAB® Compiler™ Release Notes | ![]() |
This table summarizes what's new in Version 4.1.1 (R14SP1+):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
| No | No | Fixed bugs | No |
MATLAB Compiler 4.1.1 includes bug fixes incorporated since Version 4.1 (Release 14SP1). These bug fixes include the following.
With this release, you can use the ~ character as part of the destination file name or directory on UNIX systems. For example:
zipfile = buildmcr('~/mcr')Before this release, using the ~ character as part of the destination file name or directory on UNIX systems caused the error:
Error opening '~/mcr/MCRInstaller.zip'
With this release, you can use supported versions of the Borland Compiler (see the Supported Compilers list) to build C++ shared libraries. In previous releases, Borland compilers could build C shared libraries, but building C++ shared libraries resulted in link-time errors. These errors have been resolved.
If you use the -v option to generate the verbose output of the compilation steps, MATLAB Compiler creates a log file called mccExcludedFiles.log. This file contains, if any, the list of functions that have been excluded from the compiled application. This list does not include the core MATLAB functions that are unsupported. See "Unsupported Functions" in the MATLAB Compiler User's Guide documentation.
The loadlibrary function did not work in certain cases in compiled mode. This problem has been resolved with this release of MATLAB Compiler. Note that the libraries created using MATLAB Compiler cannot be loaded into MATLAB workspace using the loadlibrary function.
In R14, before Service Pack 1, C++ applications that linked against two or more MATLAB Compiler generated C++ shared libraries would get a link-time error indicating that mclcppMlfFeval was multiply defined. In R14 Service Pack 1, this function, which is found in extern/include/mclcppclass.h, has been declared inline; this resolves the problem.
You can use the isdeployed function to determine if an MCR was started by MATLAB Compiler. The mcc command starts a new MCR. The isdeployed function will return true for this MCR, thus replicating the deployed environment.
On Windows, when mbuild (which is called by mcc) fails, you will no longer get the misleading error about -e not being an internal or an external command.
In certain scenarios, the compilation time is reduced and the size of the CTF file is smaller.
When various toolboxes are compiled, the translation files are now included in the CTF archive. This will let Japanese users see the translated output for certain toolbox messages.
In MATLAB Compiler 4.0 (R14), M-files that used the web function would compile (apparently without error), but fail to execute at run time. This occurred because a function that the web command depends on, ibrowse, was not being shipped. ibrowse is now shipped with the MCR.
![]() | Version 4.2 (R14SP2) MATLAB Compiler Software | Version 4.1 (R14SP1) MATLAB Compiler Software | ![]() |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |