You install CScout in eight steps:
csmake(under Unix) or
csmake.bat(under Windows) from the
bindirectory into a directory that is part of your path. Under Unix
/usr/local/binis a common suitable choice. Under Windows
C:\WINNT\system32is a location you could use, if your system is not better organized.
csmake.batto point to the directory where you installed the corresponding file.
etcto the final installation place you prefer (renaming it, if you wish), and arrange for the environment variable
CSCOUT_HOMEto 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_HOMEenvironment 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.
Alternativelly, the contents of the directory
will be searched in
%APPDATA%/.cscout (under Windows; it will be something like
C:\Documents and Settings\Your Name\Application Data),
the current directory's
cscout_defs.PLATFORM(where PLATFORM is the operating system and the compiler that most closely resemble your setup) as
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.
.GENERICfiles copy the
includedirectory to an appropriate location (e.g.
cscout_incs.hto specify the location where your compiler's (or the generic) include files reside.
.GENERICfile 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_doubletype and associated keyword with semantics roughly equivalent to
doubleyou would add a line in
#define quad_double doubleHave a look in the existing
cscout_defsfiles to see what might be required.
|Contents||« Previous Next (Workflow) »|