| home
topology files
command‑line options
the core API
FAQ
download and install
|
cnet's runtime environment
When initially configured and compiled,
cnet employs a number of string constants to define and
constrain its execution.
While it is anticipated that these "compiled-in" defaults will be reasonable,
there are occasions when you may wish to change one without having to
recompile all code.
At runtime,
cnet honours a number of Unix/Linux environment variables that
may override cnet's default behaviour.
Running cnet with its
-v
option will report the environment values that are being used
(along with much other information).
Depending on which Unix/Linux shell you use
(type shell> echo $SHELL to find out),
environment variables may be set in one of two ways:
| variable name |
description |
| CNETPATH |
The value of CNETPATH provides a colon-separated
list of directory names where cnet will search for
the <cnet.h> header file when compiling C protocol files.
CNETPATH is also used to locate the images displayed on the simulation map.
|
| CNETCPP |
The value of CNETCPP provides the full pathname of the C preprocessor
used to preprocess cnet topology files (if necessary).
Your system's local compiler
(typically clang or gcc)
will be invoked
with its -E option to preprocess the topology files.
|
| CNETCC |
The value of CNETCC provides the full pathname of the C compiler used to
compile the C99 protocol files.
The compiler will be invoked
with its -std=c99 option to compile the source files.
|
| CNETLD |
The value of CNETLD provides the full pathname of the program used to
link one or more object files to produce the final executable protocol.
|
| CNETFILEEXT |
The value of CNETFILEEXT provides the filename extension of
cnet's (executable) shared object files.
By default, this is ".cnet"
|
|
