You install CScout in eight steps:
cscout
, cswc
and csmake
(under Unix) or
cscout.exe
, cswc.bat
and csmake.bat
(under Windows)
from the bin
directory
into a directory that is part of your path.
Under Unix /usr/local/bin
is a common suitable choice.
Under Windows C:\WINNT\system32
is a location
you could use, if your system is not better organized.
cswc.bat
and csmake.bat
to point to the directory where you installed the corresponding file.
etc
to the
final installation place you prefer (renaming it, if you wish),
and arrange for the environment variable CSCOUT_HOME
to point to it.
As an example, under Unix you would probably have the directory
installed as /usr/local/etc/cscout
.
Under Unix, you can permanently set the CSCOUT_HOME
environment variable by editing a file named
.profile
(sh and derivative shells)
or
.login
(csh and derivative shells)
in your home directory.
Under Windows (NT, 2000, XP, and later editions),
you can set environment variables through an option in:
Control Panel - System - Advanced - Environment Variables,
on Windows-95/98/Me you will need to edit the file c:\autoexec.bat
.
Alternativelly, the contents of the directory etc
will be searched in $HOME/.cscout
and
the current directory's .cscout
directory.
cscout_incs.PLATFORM
and
cscout_defs.PLATFORM
(where PLATFORM is the operating system and the compiler
that most closely resemble your setup)
as cscout_incs.h
and cscout_defs.h
.
In most cases you want CScout to process your code using the include files of the compiler you are normally using. This will allow CScout to handle programs using the libraries and facilities available in your environment (e.g. Unix system calls or the Windows API). If your programs are written in ANSI C and do not use any additional include files, you can use the .GENERIC files and rely on the include files supplied with the CScout distribution.
.GENERIC
files
copy the include
directory to an appropriate location
(e.g. /usr/local/include/cscout
under Unix).
cscout_incs.h
to specify the location
where your compiler's (or the generic) include files reside.
.GENERIC
file set and
add suitable definitions to sidestep the problems caused by the
extensions your compiler supports.
As an example,
if your compiler supports a quad_double
type and associated
keyword with semantics roughly equivalent to double
you would add a line in cscout_incs
:
#define quad_double doubleHave a look in the existing
cscout_defs
files to see
what might be required.
Contents | « Previous Next (Workflow) » |