Execution environment set-up
----------------------------

Before you start examining the first phase of the design methodology,
you first have to set up an execution environment for ALLIANCE tools. 
Unless you set some environment variables up, each ALLIANCE tool 
execution fails.

ALLIANCE needs to know several things before it can work appropriately.

1) library path
---------------

First thing to know is the actual location of standard-cells.
Take a look at your current directory path. The end of the
pathname must contain the string "alliance-2.0/tutorials/ADDACCU".
Cells are located in something...alliance-2.0/cells.
It is important to note that we distinguish between two sets
of cells, the basic standard-cell library, and the pad library.

Practically, if your ALLIANCE login name is "alliance" and the
alliance account is located in /users/guests, standard-cells can be found
in /users/guests/alliance-2.0/cells/scr and
pad cells in /users/guests/alliance-2.0/cells/ring/pad12

please enter the following command accordingly:

> setenv MBK_CATA_LIB .:/users/guests/alliance-2.0/cells/scr:/users/guests/alliance-2.0/cells/ring/pad12

This setenv instructs ALLIANCE tools to search standard-cells or blocks
in the current directory, then in
    /users/guests/alliance-2.0/cells/scr
and at last in
    /users/guests/alliance-2.0/cells/ring/pad12

At this point, ALLIANCE just need to know how to search the behavior file
in the current directory. Character '.' in the setenv is used for that
purpose.


2) working directory
--------------------

You must specify the location where the generated ALLIANCE
files are to be located.

please enter the following command:

> setenv MBK_WORK_LIB .

In your case, the working directory is the current directory.

Press <return> to continue.
