BCG_OPEN manual page
Table of Contents

Name

bcg_open - OPEN/CAESAR connection for graphs encoded in the BCG format

Synopsis

bcg_open [bcg_options] filename[.bcg] [cc_options] user[.a|.c|.o] [user_options]

Description

Taking as input a BCG graph filename.bcg and an OPEN/CAESAR program user[.a|.c|.o], bcg_open generates an executable program user performing appropriate calls to the BCG programs and the C compiler. Finally, user is executed.

According to the principles of the OPEN/CAESAR architecture, user is obtained by combining three different modules:

Processing of the Graph Module

A dynamic library corresponding to filename.bcg may be generated if necessary.

Processing of the Exploration Module

The exploration module user[.a|.c|.o] is supposed to contain an OPEN/CAESAR application program, such as exhibitor, evaluator, terminator...

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, bcg_open attempts to fetch it in the OPEN/CAESAR binary library $CADP/bin.`arch`.

If user.c is not present in the current directory, bcg_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, bcg_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, bcg_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.

Determination of Include or Link Mode

Only the ``link mode'' of OPEN/CAESAR is supported by bcg_open.

General Options

The following bcg_options are currently supported: -version, -create, -update, -remove, -cc, and -tmp. See the bcg manual page for a description of these options.

Particular Options

The cc_options, if any, are passed to the C compiler.

The user_options, if any, are passed to user.

Environment Variables

See the bcg manual page for a description of the environment variables used by all the BCG application tools.

Exit Status

Exit status is 0 if everything is alright, 1 otherwise.

Authors

Renaud Ruffiot and Hubert Garavel

Operands

filename.bcg
BCG graph (input)

filename@1.o
dynamic library (input or output)

user.a      
exploration module (archive, input)

user.c      
exploration module (source, input)

user.o      
exploration module (object code, input)

user       
executable program (output)

Files

$CADP/com/bcg_open
``bcg_open'' shell script

$CADP/bin.`arch`/libbcg_open.a
``bcg_open'' static library

$CADP/incl/caesar_*.h
OPEN/CAESAR interfaces

$CADP/bin.`arch`/libcaesar.a
OPEN/CAESAR library

$CADP/src/open_caesar/*.c
exploration modules (source)

$CADP/bin.`arch`/*.a
exploration modules (archive)

$CADP/bin.`arch`/*.o
exploration modules (object code)

See the bcg manual page bcg for a description of the other files).

See Also

bcg , caesar.open

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.

Bugs

Please report bugs to Hubert.Garavel@inria.fr


Table of Contents