CRIS/SIS: ACEware System
Making the level1_1 Package

These are the guidelines for the creation of the ACEware level1_1 library.

Step 1: Define the environment variables ACE_WARE and CC.

VERY IMPORTANT DISTINCTION!: If you are installing this package for the first time into your ACEware system, the environment variable ACE_WARE needs to be defined as the base directory of your ACEware installation. If, on the other hand, you are updating a package into an ACEware system which is already in use, then ACE_WARE needs to be defined as the base of your shadow installation. In either case, after defining ACE_WARE, you should see the following:

% cd $ACE_WARE
% ls
RCSfiles/       idl/            lib/            pkgs/
exe/            include/        man/
%

As a concrete example, if I were installing the initial version of the ACEware system at SRL, I would define

setenv ACE_WARE /home/idunn1/ACEware

which, in fact, is where the official installation of ACEware is at SRL. On the other hand, if I were instead updating the level1 package, I might chose to place the shadow directory tree in my home directory to work on making the new release without interfering with the use of the ACEware system by others. In that case, while working on the make of the new level1 package, I would define

setenv ACE_WARE /home/darkalf/bruce/shadow

(See the shadow installation notes for more details on creating this shadow workspace.)

CC should be defined as your favorite POSIX/ANSI C compiler, e.g.,

setenv CC gcc

Step 2: Go to the level1_1 library's source directory.

cd to ${ACE_WARE}/pkgs/level1_1/src/lib.

Step 3: Make the level1_1 Library.

Check the Makefile. Most likely you will not need to change much if anything.

Type "make distill" to clean up (so no old libraries or object files are mistaken for your current make.) Type "make".

Check that a new level1_1 library is in place in the level1_1 package's lib directory:

% ls ${ACE_WARE}/pkgs/level1_1/lib
liblevel1_1.a

Do a "make clean" if desired to remove unneeded object files (which were used in creating the library.)

Step 4: Go to the level1_1 executable's source directory.

cd to ${ACE_WARE}/pkgs/level1_1/src/prog.

Step 5: Make the level1_1 executables.

Check the Makefile. Most likely you will not need to change much if anything.

Type "make distill" to clean up (so no old executables or object files are mistaken for your current make.) Type "make".

Check that new level1_1 executables are in place in the level1_1 package's exe directory:

% ls ${ACE_WARE}/pkgs/level1_1/exe
BrowseCrisPigeonHole  L1CrisPigeonHole
BrowseSisPigeonHole   L1SisPigeonHole

Do a "make clean" if desired to remove unneeded object files (which were used in creating the library.)

You have finished making the level1_1 package.

Back to Initial Installation Notes / Package Update Notes

Return to Table of Contents

bruce