Files
motorBase/config/RELEASE
T
Ron Sluiter 45b33d8064 Merged from R4-3.
- Comment: MPF_SERIAL must be defined if either serial or GPIB communication is required.
- Updated support modules to latest releases; mpfSerial R1-2, MPF R1-6, EPICS base R3-13-4
2001-04-20 19:28:22 +00:00

37 lines
1.3 KiB
Plaintext

# RELEASE - Location of external products
#
# (Architecture dependent declarations should go into RELEASE.<arch>)
#
# Note: This file will be scanned to automatically generate
# include path definitions etc.
# The order of the following declarations will be retained
# within those definitions.
#
# Add your declarations here
#SUPPORT=/usr/local/epics/3.13.2/support
# Define the following if MPF is defined (i.e., if either serial
# or GPIB motor controller support is required).
#MPF_SERIAL=$(SUPPORT)/mpfSerial/mpfSerial1-2
# If the EPICS GPIB Module from Benjamin Franksen is used, then remove the '#'
# from the following and modify the motorApp/CommSrc/Makefile.Vx file per
# instructions found there. If GPIB driver support is from EPICS base, then
# leave this line commented out.
#GPIB=$(SUPPORT)/gpib
# If any motor controller communication mechanism besides the VME backplane is
# required, then MPF must be defined.
#MPF=$(SUPPORT)/mpf/mpf1-6
#EPICS_BASE=$(SUPPORT)/base/3-13-4
# The following must be defined if motorExApp is to be built.
#TEMPLATE_TOP=$(EPICS_BASE)/templates/makeBaseApp/top
#MSITOP=/usr/local/epics/extensions
# The following must be defined if the "WithMPF" example in motorExApp is to
# be built.
#MPF_GPIB=$(SUPPORT)/mpfGpib/mpfGpib1-3