EPICS application source/release control Page: 2 of 20
This report is part of the collection entitled: Office of Scientific & Technical Information Technical Reports and was provided to Digital Library by the UNT Libraries Government Documents Department.
The following text was automatically extracted from the image on this page using optical character recognition software:
A new method of adding application specific source files is now supported. This method
allows the user to create and use simple Makefiles in an application source directory (see
section "Adding Application Specific Source Files" on page 13 for more information).
Makefile templates are provided. Imakefiles and the Buildit command are no longer
necessary. Targets built from these Makefiles will reside in target-architecture specific
subdirectories of this source directory. New makefile targets, clean, depends and build,
have been added to support the Makefile method. For upward compatibility, Imakefiles and
the Buildit command are still supported but their use is not encouraged.
There are two changes to the Imakefile method. Depends are no longer available for Unix
architectures and the "gmake buildMakefiles" command now executes "gmake clean"
before executing "gmake" after the Makefiles are rebuilt.
Features The Application Source/Release Control System (appSR) provides the following features:
Multiple Applications: The entire system is composed of an arbitrary number of applications.
Source/Release Control: All files created or modified by the application developers can be
put under sccs, which is a Unix source/release control utility.
Multiple Developers: It allows a number of application developers to work separately during
the development phase but combine their applications for system testing and for a production
Makefiles: Makefiles are provided to automatically rebuild various application components.
For C and state notation programs Makefile templates are provided. For compatibility
Imakefiles are supported.
Definitions Application System Area: The set of directories and files managed by the tools described in
this document. Everything is stored in one directory tree. The top level directory contains
information common to all applications in this area as well as a subtree for each application.
Application: A subtree under the application system area that contains all the files for a single
Application Shadow Area: A set of directories and soft links to an application system area
for use by the application developer. It appears to the user just like a copy of the system area.
It is used for individual development and testing of application changes/fixes.
Application Production Area: A copy of a working application system area for use by
Classes of Users Application System Manager: The Application System Manager is responsible for the
Application System area.
Application Developer: Anyone who tests, modifies, or extends an application's software. If
multiple developers are working on the same system each should develop in a private shadow
Application Production Manager: A person responsible for production application software.
EPICS Application Source/Release Control
Document Revision: Draft
Here’s what’s next.
This report can be searched. Note: Results may vary based on the legibility of text within the document.
Tools / Downloads
Get a copy of this page or view the extracted text.
Citing and Sharing
Basic information for referencing this web page. We also provide extended guidance on usage rights, references, copying or embedding.
Reference the current page of this Report.
Zieman, B.; Anderson, J. & Kraimer, M. EPICS application source/release control, report, December 31, 1995; Illinois. (https://digital.library.unt.edu/ark:/67531/metadc668962/m1/2/: accessed April 18, 2019), University of North Texas Libraries, Digital Library, https://digital.library.unt.edu; crediting UNT Libraries Government Documents Department.