MATLAB® Compiler Release Notes Previous page   Next Page

Major Bug Fixes

MATLAB Compiler 4.1.1 includes bug fixes incorporated since Version 4.1, which was released in Release 14SP1. These bug fixes include the following.

buildmcr Function Supports Use of ~ in Filename on UNIX

With this release, you can use the ~ character as part of the destination filename or directory on UNIX systems. For example

Previous to this release, using the ~ character as part of the destination filename or directory on UNIX systems caused the error

C++ Shared Libraries Fully Supported with Borland Compilers

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.

Excluded Functions List Stored in Log File

If you use the -v option to generate the verbose output of the compilation steps, the 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. Refer to the MATLAB Compiler User's Guide for the unsupported functions.

loadlibrary Function Works in Compiled Mode

The loadlibrary function did not work in certain cases in compiled mode. This problem has been resolved with this release of the MATLAB Compiler. Note that the libraries created using the MATLAB Compiler cannot be loaded into the MATLAB workspace using the loadlibrary function.

mclcppMlfFeval No Longer Multiply-Defined

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.

MCR Started by MATLAB Compiler Returns true for isdeployed

You can use the isdeployed function to determine if an MCR was started by the MATLAB Compiler. The mcc command starts a new MCR. The isdeployed function will return true for this MCR, thus replicating the deployed environment.

Misleading -e Error Is Resolved

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.

Reduced Compilation Time and Size of the CTF File

In certain scenarios, the compilation time is reduced and the size of the CTF file is smaller.

Translation Files for Various Toolboxes Included in the CTF File

When various toolboxes are compiled, the translation files are now included in the CTF archive. This will enable Japanese users to see the translated output for certain toolbox messages.

web Function Compiles Successfully

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.


Previous page  MATLAB Compiler 4.1.1 Release Notes Upgrading from an Earlier Release Next page

© 1994-2005 The MathWorks, Inc.