| MATLAB® Compiler™ | ![]() |
As of R2008a, CTF data is now automatically embedded directly in the C/C++, main and Winmain, shared libraries and standalones by default. In order to override this default functionality, you must compile with the option -C Do Not Embed CTF Archive By Default.
If you use the mcc -C option to specify that a separate CTF file is to be generated, you can add environment variables to specify various options, such as:
Defining the location where you want the CTF archive to be extracted
Adding diagnostic error printing options that can be used when extracting the CTF, for troubleshooting purposes
Tuning the MCR Component Cache size for performance reasons.
Use the following environment variables to change these settings.
| Environment Variable | Purpose | Notes |
|---|---|---|
| MCR_CACHE_ROOT | When set to the location of where you want the CTF archive to be extracted, this variable overrides the default per-user component cache location | N/A |
| MCR_CACHE_VERBOSE | When set, this variable prints details about the component cache for diagnostic reasons. This can be very helpful if problems are encountered during CTF archive extraction. | N/A |
| MCR_CACHE_SIZE | When set, this variable overrides the default component cache size. | The initial limit for this variable is 32M (megabytes). This may, however, be changed after you have set the variable the first time. Edit the file .max_size, which resides in the file designated by running the mcrcachedir command, with the desired cache size limit. |
Note If you run mcc specifying conflicting wrapper and target types, the CTF will not be embedded into the generated component. For example, if you run: mcc -W lib:myLib -T link:exe test.m test.c the generated test.exe will not have the CTF embedded in it, as if the user has specified a -C option to the command line. |
![]() | Interfacing M-Code to C/C++ Code | Using Pragmas | ![]() |
| © 1984-2008- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |