The Source Integrity Professional Edition User Guide - MKS

Using CC
Generic
Command-line
Format
Using the Generic CC Interface
UNIX-based systems, the configuration file is /etc/compiler.ccg.
Alternatively, you can set the CCG environment variable to point to
another configuration file.
The online reference for cc provides information on writing your
own configuration files, if you want to use an unsupported compiler
or linker. Certainly, the best way to start is copy and modify one of
the provided configuration files.
The cc command is installed in the same directory as the make
command. If this directory is in your search rules, you can call the
command by using the name cc.
The supplied default rules file defines the CC macro to refer to your
favorite C compiler. For example, if you use the Borland C compiler,
it would contain
CC = bcc
LD = bcc
To use CC, you would edit your default rules file to
CC = cc
LD = cc
From this point on $(CC) and $(LD) invoke cc instead of your
chosen compiler or linker. Since the installation process sets up
appropriate configuration files, cc converts its generic command line
to the format required by your chosen compiler and linker before
invoking that compiler or linker.
The cc command uses the following generic command-line format
for compilation:
cc -c [options] file…
where each option begins with a dash.
For example, the recommended way of selecting compiler memory
models is with the -mmodel option. If you are using Microsoft C
version 6.0 and want a large model program, you enter
cc -c -ml file
instead of using the /AL option. You could still use the /AL option, but
your makefile would not be portable.
The files specified on the command line are the C source files you
want compiled. cc invokes your chosen compiler to compile each
source file.
User Guide 303