%MCC MATLAB to C/C++ Compiler (Version 2.0).
%   MCC [-options] fun [fun2 ... ]
%   
%   Translate fun.m to fun.c or fun.cpp, and optionally create any supported binary
%   file.  Write any resulting files into the current directory, by default.
%   
%   If more than one M-file is specified, a C or C++ file is generated for each
%   M-file.
%   
%   If C files are specified, they are passed to MEX or MBUILD along with any
%   generated C files.
%   
%   If conflicting options are presented to MCC, the rightmost conflicting option is
%   used.
%   
%   NOTE to Compiler 1.2 users: The options for Compiler 2.0 are somewhat different
%   from Compiler 1.2.  Type "mcc -V1.2 -?" to obtain the online help for
%   Compiler 1.2.
%   
%   In order to assist in migrating to this new release, we have prepared a
%   quick-reference card which contains both the Compiler 1.2.1 and the Compiler 2.0
%   options.  You can access this pdf file by selecting "Online Manuals" from the
%   HELPDESK.
%   
%   OPTIONS:
%   
%   A <keyword>:<setting> Specify annotation.  <keyword> can be one of "annotation",
%       "line", or "debugline".  "annotation" specifies how much of the source
%       M-file the Compiler should write into the generated output file as comments.
%       The <setting> following "annotation" can be "all" (default), "comments", or
%       "none", specifying all M-code, only M-code comments, and no M-code
%       respectively.  "line" specifies the presence or absence of #line directives
%       which map lines in a generated C/C++ file to corresponding lines in the
%       source M-file. The <setting> following "line" can be "off" (default), or
%       "on", specifying absence or presence of #line directives. "debugline"
%       specifies whether error messages report the source file name and line
%       number.  The <setting> following "debugline" can be "off" (default), or
%       "on", specifying the absence or presence of source file and line number
%       information in run-time error messages.
%   
%   B <filename> Specify bundle file.  <filename> is a text file containing Compiler
%       command line options.  The Compiler behaves as if the "-B <filename>" were
%       replaced by the contents of the bundle file. Newlines appearing in these
%       files are allowed and are treated as whitespace.
%   
%   c   C only.  Translate M-file to C, but do not produce a MEX-file or stand-alone
%       application.  This is equivalent to "-T codegen" as the rightmost argument
%       on the command line.
%   
%   d <directory> Output directory.  All generated files will be put in <directory>.
%   
%   F list.  List the <option>s available in the next form of the command, together
%       with their current values and a short explanation.
%   
%   F <option>:<number> Typesetting format options.  Assign the value <number> to
%       the formatting option <option>.  See "F list" for <option>s.
%   
%   f <filename> Use the specified options file when calling MEX or MBUILD.  This
%       allows you to use different ANSI compilers.  This option is a direct
%       pass-through to the MEX or MBUILD script.  See the "Application Program
%       Interface Guide" for more information.
%   
%   g   Debug.  Include debugging symbol information.
%   
%   h Compile helper functions by default.  Any M-functions called will be compiled
%       into the resulting MEX-file or stand-alone application.
%   
%   I <path> Include path.  Add <path> to the list of paths to search for M-files.
%       The MATLAB path is automatically included when running from MATLAB, but NOT
%       when running from DOS or the Unix shell.  See "help mccsavepath".
%   
%   L <option> Language.  Specifies target language.  <option> can be either
%       "C" for C or "Cpp" for C++.
%   
%   l   Line.  Generates code that reports file name and line numbers on run-time
%       errors.  (Equivalent to -A debugline:on)
%   
%   m   Macro that generates a C stand-alone application.  This is equivalent to
%       "-t -W main -L C -h -T link:exe".  Note:  the "-h" means that helper
%       functions will be included.
%   
%   M "<string>" Pass <string> to the MBUILD or MEX script used to build an
%       executable. If -M is used multiple times, the rightmost occurrence is used.
%   
%   o <outputfilename> Output name.  Set the name of the final executable output
%       (MEX or stand-alone application) to <outputfilename>.  A suitable, possibly
%       platform-dependent, extension is added to <outputfilename> (e.g., ".exe" for
%       PC stand-alone applications, ".mexsol" for Solaris MEX-files).
%   
%   p   Macro that generates C++ stand-alone application.  This is equivalent to
%       "-t -W main -L Cpp -h -T link:exe".  Note:  the "-h" means that helper
%       functions will be included.
%   
%   S   Macro that generates Simulink C-MEX S-Function.  This is equivalent to
%       "-t -W simulink -L C -T link:mex".  Note:  the absence of "-h" means that
%       helper functions will not be included.
%   
%   t   Translate M code to target language.  Translate any M-functions specified on
%       the command line to C or C++ functions.  This option is included in all
%       macro options.  Omitting it allows the generation of wrapper C/C++ files
%       without generating the C/C++ files corresponding to M-files.
%   
%   T <option> Specify target phase.  <option> must be "codegen",
%       "compile:<bintype>", "link:<bintype>", or "lib:<bintype>", where <bintype>
%       must be one of "mex", "exe", or "lib".  If <option> is "codegen", the
%       Compiler stops after performing M-to-C/C++ translation and wrapper file
%       generation.  If <option> starts with "compile:", the Compiler performs the
%       previous step and then compiles the C/C++ file(s) into object file(s).  The
%       built object file(s) are suitable for linking into a MEX-file if <bintype>
%       is "mex", into a stand-alone application if <bintype> is "exe", or into a
%       shared library if <bintype> is "lib".  If <option> begins with "link:", the
%       Compiler performs both previous steps and then links the object code into a
%       MEX-file (if <bintype> is "mex"), a stand-alone application (if <bintype> is
%       "exe"), or a shared library (if <bintype> is "lib").
%   
%   u <number> Specify that the number of inputs to a generated Simulink S-function
%       should be <number>.  Valid only if either "-S" or "-W simulink" option has
%       also been specified.
%   
%   v   Verbose.  Show compilation steps.
%   
%   V1.2 Access Compiler 1.2.1. The options described in this text are for Compiler
%       2.0 only. Type "mcc -V1.2 -?" to obtain the online help for Compiler 1.2.1.
%   
%   w list.  List the <msg> strings allowed in the next form of the command,
%       together with the full text of the warning messages to which they
%       correspond.
%   
%   w <option>[:<msg>] Warnings.  The possible options are "enable", "disable", and
%       "error".  If "enable:<msg>" or "disable:<msg>" is specified, enable or
%       disable the warning associated with <msg>.  If "error:<msg>" is specified,
%       enable the warning associated with <msg> and treat any instances of that
%       warning as an error.  If the <option> but not ":<msg>" is specified, the
%       Compiler applies the action to all warning messages.  For compatibility with
%       Compiler 1.2, "-w" (with no option) is the same as "-w enable".
%   
%   W <option> Wrapper functions.  Specify which type of wrapper file should be
%       generated by the Compiler.  <option> can be one of "mex", "main",
%       "simulink", "lib:<string>", or "none" (default).  For the lib wrapper,
%       <string> contains the name of the generated header, source and exports file.
%   
%   x   Macro that generates a MEX file.  This is equivalent to
%       "-t -W mex -L C -T link:mex".  Note:  the absence of "-h" means that helper
%       functions will not be included.
%   
%   y <number> Specify that the number of outputs from a generated Simulink
%       S-function should be <number>.  Valid only if either "-S" or "-W simulink"
%       option has also been specified.
%   
%   Y <license.dat file> Override default license.dat file with specified
%       argument.
%   
%   z <path>  Specify the path to use for library and include files.
%       This option uses the specified path for the Compiler libraries
%       instead of MATLABROOT.
%   
%   ?   Help.  Display this help message.
%   
%   EXAMPLES:
%   
%   Make a C translation and a MEX-file for myfun.m:
%       mcc -x myfun
%   
%   Make a C translation and a stand-alone executable for myfun.m:
%       mcc -m myfun
%   
%   Make a C++ translation and a stand-alone executable for myfun.m:
%       mcc -p myfun
%   
%   Make a C translation and a Simulink S-function for myfun.m
%    (using dynamically sized inputs and outputs):
%       mcc -S myfun
%   
%   Make a C translation and a Simulink S-function for myfun.m
%    (explicitly calling for one input and two outputs):
%       mcc -S -u 1 -y 2 myfun
%   
%   Make a C translation and stand-alone executable for myfun.m.  Look for
%    myfun.m in the directory /files/source, and put the resulting C files and
%    executable in the directory /files/target:
%       mcc -m -I /files/source -d /files/target myfun
%   
%   Make a C translation and a MEX-file for myfun.m.  Also translate and include 
%    all M-functions called directly or indirectly by myfun.m.  Incorporate the 
%    full text of the original M-files into their corresponding C files as C 
%    comments:
%       mcc -x -h -A annotation:all myfun
%   
%   Make a generic C translation of myfun.m:
%       mcc -t -L C myfun
%   
%   Make a generic C++ translation of myfun.m:
%       mcc -t -L Cpp myfun
%   
%   Make a C MEX wrapper file from myfun1.m and myfun2.m:
%       mcc -W mex -L C myfun1 myfun2
%   
%   Make a C translation and a stand-alone executable from myfun1.m and myfun2.m
%    (using one mcc call):
%       mcc -m myfun1 myfun2
%   
%   Make a C translation and a stand-alone executable from myfun1.m and myfun2.m
%    (by generating each output file with a separate mcc call):
%       mcc -t -L C myfun1                 % yields myfun1.c
%       mcc -t -L C myfun2                 % yields myfun2.c
%       mcc -W main -L C myfun1 myfun2     % yields myfun1_main.c
%       mcc -T compile:exe myfun1.c        % yields myfun1.o
%       mcc -T compile:exe myfun2.c        % yields myfun2.o
%       mcc -T compile:exe myfun1_main.c   % yields myfun1_main.o
%       mcc -T link:exe myfun1.o myfun2.o myfun1_main.o
%   
%    Note: on PCs, filenames ending with .o above would actually end with .obj.
%
%
%   See also COMPILER/FUNCTION, MCCSAVEPATH, REALONLY, REALSQRT, REALLOG, 
%            REALPOW, COMPILER_SURVEY, COMPILER_BUG_REPORT.

% Copyright (c) 1984-1998 by The MathWorks, Inc.
% All Rights Reserved.

error('MEX file not present');
