| Version 1.9 Build 803
|
|
Next: Documentation
Up: Where to Look
Previous: Who Can Help Me?
There are several major directory areas you should understand if you
wish to program or write documentation for AIPS++. You may wish
to refer to the AIPS++ System Manual
for further details.
- There are the master source directories, which contain the
sources of code and documentation 1.1. Since these are master sources, you cannot
directly modify them, rather you must modify them by checking them into
your personal (see below) directory, modify them, and then check
them back.
- You modify source (program or documentation) in your personal
directories. These directories shadow the master directories.
Because new directories are created or deleted on occasion, you will
sometimes need to run the mktree program to reflect any directory
additions or deletions in the master directories.
- Processed documentation directories. Documentation which has been
processed (normally by being turned into PostScript and HTML) are placed into
common directory tree. During development of the documents you will be
working in your personal directories.
- Binary directories. These are where common (shared among all
programmers) programs and libraries go. These are architecture
dependent. During class and program development you will be working in
your personal directories.
The exact location of these directories will depend on how your local
system was set up, but will be of the following form:
- master
- /aips++/code
- personal
- /aips++/code
- processed documentation
- /aips++/docs
- binary
- /aips++/sun4sol_gnu or whatever architecture(s) you have at your
installation.
Sometimes instead of /aips++ your common directories will be
under /aips2/aips++ or /u/aips++ or some other location.
You will need to ask locally.
Similarly, your personal directory need not be directly under your home
directory -- you may put it anywhere you have Unix "write" permission.
The directory location of a source file is often written as something like
code/doc/reference/Coding.latex. If you are working on it in your
personal directory you would prepend this path with
/aips++ and if you wanted to look at the master version you
would prepend the path with /aips++ (or wherever your common
installation is).
Next: Documentation
Up: Where to Look
Previous: Who Can Help Me?
Contents
Index
Please send questions or comments about AIPS++ to aips2-request@nrao.edu.
Copyright © 1995-2000 Associated Universities Inc.,
Washington, D.C.
Return to AIPS++ Home Page
2004-08-30