caesar , caesar.adt , and the C compiler, avoiding recompilation whenever possible. Finally, user is executed.
According to the principles of the OPEN/CAESAR architecture, user is obtained by combining three different modules:
caesar.open automatically invokes caesar.adt if the abstract data type implementation spec.h does not exist or is out of date. However, if spec.h exists and has not been generated using caesar.adt , it will not be overwritten, even if it is out of date (in this case, a warning is issued).
caesar.open takes into account the dependencies possibly created by spec.c, spec.h, spec.t, and spec.f.exhibitor , terminator , xsimulator ...
The exploration module can be supplied in three different forms. It can be either an archive file (with .a suffix), or a source C program (with .c suffix) or an object code file (with .o suffix).
If user.a is not present in the current directory, caesar.open attempts to fetch it in the OPEN/CAESAR binary library $CADP/bin.`arch`.
If user.c is not present in the current directory, caesar.open attempts to fetch it in the OPEN/CAESAR source library $CADP/src/open_caesar.
If user.o is not present in the current directory, caesar.open attempts to fetch it in the OPEN/CAESAR binary library $CADP/bin.`arch`.
If no suffix (.a, .c, .o) is specified on the command line for the exploration module user, caesar.open will make successive attempts to fetch this exploration module: first, as a source C program with .c suffix; then as an archive file with .a suffix; finally as an object code file with suffix .o.
If the exploration module is in archive form or in object code form, only the link mode is allowed.
The options cc_opt, if any, are passed to the C compiler.
The options user_opt if any, are passed to user.
caesar.open spec.lotos -O user.a
caesar.open spec.lotos -O user.c
caesar.open spec.lotos -O user.o
caesar.open -comments -gc spec.lotos user -size 1000
Additional information is available from the CADP Web page located at http://cadp.inria.fr
Directives for installation are given in files $CADP/INSTALLATION_*.
Recent changes and improvements to this software are reported and commented in file $CADP/HISTORY.Hubert.Garavel@inria.fr