Step-by-step guide to building a TAS2 program

1. Plan your activity

Think about what tables your module requires and how they are related.

2. Log in to

3. newgrp nsdtpc

This requires that you have already put the following lines in your .cshrc file

if ( -e !eostpc/login_eos.csh) then	
source ~eostpc/login_eos.csh

This sets up the TAS 2 environment for EOS whenever you change your group ID to nsdtpc.

4. Set up a new code module

5. tas2_menu

6. edit your code

You now edit your code following the EOS style guide and put the sources in PKG/src.

7. cvs add file1 [file2 file3 ...]

All files that need to be added to the library are added with this command. This applies to all source code, include files and documentation files, but not machine binary files such as object code and executable images.

You should check the man page for an accurate list of options and parameters.

Note that files are NOT checked in to the code repository (CVS) unless you explicitly execute cvs add for all files. In order to verify which files are checked in to CVS do " cat CVS/Entries".

8. cvs commit

Use the cvs commit command to check in or commit the changes, add requests, remove requests that you have made to the Repository. When you execute the commit command cvs will prompt you for a comment by popping up an editer (vi by default, set your preference with the EDITOR environment variable).

9. make lib

Compile the object library for your package by executing this command in the PKG/lib directory. If your package needs special procedures, beyond what comes in the default PKG/lib/Makefile, in order to compile the object library you should put these details into PKG/lib/Makefile under the lib target. Feel free to consult the librarian or other experts about how to do this.

10. prepare the .mid file

There are effectively two levels of .mid files, one for each anlaysis module and another for an executable program. Each analysis module should have its own .mid file with only references for that module. The .mid file for bilding an executable program should only #include .mid files for each module. This file should be stored in the PKG/src directory with a .mid extension. As with other source files this needs to be stored in the library with the cvs add command. See the TAS manual for more information on .mid files.

11. Build TAS executable

See TAS Makefile example for a description of the procedure to build your executable program. Note that this procedure puts the executable file in the PKG/bin/sun4 directory.

12. run your TAS program

You should now be ready to execute your TAS program and EOS having some real fun.

13. make install

After your changes are verified to be working you need to put your include files and object library into the "public library" directories. This is accomplished by typing make installin the PKB/lib directory.

Last modification: 8-March-1995

Back to TAS2 Intro