| Version 4.1 (R14SP1) MATLAB Compiler Release Notes | |
This table summarizes what's new in Version 4.1 (R14SP1):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
| Yes Details below | No | Fixed bugs | No |
New features and changes introduced in this version are:
You can use MATLAB Compiler 4.1 on supported Solaris systems to create redistributable, standalone applications or software components. These applications or components can then be deployed to other Solaris systems.
We encourage you to use this beta version for Solaris and we appreciate your feedback. We expect to release a fully qualified version of MATLAB Compiler for Solaris as soon as possible.
The buildmcr command that ships with MATLAB Compiler 4.1 may fail on some Solaris systems. You must upgrade your buildmcr command if you see the error message:
"Could not redirect CTFARCHIVER output to the MATLAB Desktop"
We recommend that all Solaris users upgrade their buildmcr command. For instructions on how to upgrade, see our Support site and search for "Solaris BUILDMCR." This upgrade is not necessary for Windows or Linux users.
Development Machine. To run a MATLAB Compiler generated application on your development machine, add the following directories to your dynamic library path.
Note For readability, the following command appears on separate lines, but you must enter it all on one line. |
setenv LD_LIBRARY_PATH
/usr/lib/lwp:
matlabroot/bin/sol2:
matlabroot/sys/os/sol2:
matlabroot/sys/java/jre/sol2/jre1.4.2/lib/sparc/native_threads:
matlabroot/sys/java/jre/sol2/jre1.4.2/lib/sparc/client:
matlabroot/sys/java/jre/sol2/jre1.4.2/lib/sparc:
matlabroot/sys/opengl/lib/sol2:${LD_LIBRARY_PATH}
setenv XAPPLRESDIR <matlabroot>/X11/app-defaultsTarget Machine. To run a MATLAB Compiler generated application on a target machine (a machine without MATLAB that has the MCR installed), add the following directories to your dynamic library path.
Note For readability, the following command appears on separate lines, but you must enter it all on one line. |
setenv LD_LIBRARY_PATH
/usr/lib/lwp:
mcr_root/runtime/sol2:
mcr_root/sys/os/sol2:
mcr_root/sys/java/jre/sol2/jre1.4.2/lib/sparc/native_threads:
mcr_root/sys/java/jre/sol2/jre1.4.2/lib/sparc/client:
mcr_root/sys/java/jre/sol2/jre1.4.2/lib/sparc:
mcr_root/sys/opengl/lib/sol2:${LD_LIBRARY_PATH}
setenv XAPPLRESDIR <mcr_root>/X11/app-defaults<mcr_root> is the directory where the MCR is installed.
On Solaris, the only compiler that MATLAB Compiler supports is the Sun compiler. If you are a Solaris user who is licensed to use the Sun compiler, you can redistribute the Sun sunperf and dependent libraries, including BLAS, to your end users. For more information, consult your Sun license agreement.
The MCRInstaller now supports the installation of multiple versions of the MCR on a target machine. This allows applications compiled with different versions of the MCR to execute side by side on the same machine.
If multiple versions of the MCR are not desired on the target machine, you can run Add or Remove Programs from the Control Panel to remove any of the previous versions. This can be done either before or after installation of a more recent version of the MCR, as versions can be installed or removed in any order.
The only caveat to installing a new version of the MCR is that you cannot automatically install version 7.0 in the same directory as a previously installed version of the MCR. This restriction applies only to version 7.0 of the MCRInstaller. If you must install version 7.0 in the same directory as a previous version, you should first run the version 7.0 MCRInstaller and select that directory. After the installation completes, you should manually add the MCR run-time directory <TargetDir>\v70\runtime\win32 to the system path.
MATLAB Compiler 4.1 includes bug fixes incorporated since Version 4.0.1, which was released via the Web in July 2004. These bug fixes include the following.
In MATLAB Compiler 4.0 (Release 14), users were not able to deploy MATLAB applications that used certain Java files. For example, you could not deploy the Database Toolbox functions. This bug has been fixed in this release.
The SET_PARAM error that was generated when an application was deployed to a non-U.S. locale system has been fixed.
On Windows, the problem of printing figure windows has been resolved and should work as expected.
In Release 14 on Windows, MATLAB Compiler generated applications that used the pause command would occasionally hang. This was more likely to happen if you called pause frequently or you used very small timeout values. This problem has been resolved.
| Version 4.1.1 (R14SP1+) MATLAB Compiler | Version 4.0.1 (R14+) MATLAB Compiler | |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |