This document describes how to convert a R3.14.5 application so that it builds with release R3.14.6.
Change " include $(TOP)/config/CONFIG_APP" to "include $(TOP)/configure/CONFIG"
If they do not already exist, add the lines
DIRS += $(wildcard *ioc*)
DIRS += $(wildcard as*)
Change "include $(TOP)/config/RULES.iocBoot" to "include $(TOP)/configure/RULES_DIRS"
Change "include $(TOP)/config/CONFIG_APP" to "include $(TOP)/configure/CONFIG"
Change
ARCH = <old arch specification e.g. mv167>
to
ARCH = <new arch specification e.g. vxWorks-68040>
Change "include $(TOP)/config/RULES.ioc" to "include $(TOP)/configure/RULES.ioc"
If it exists remove the line
buildInstall: cdCommands
Add the line
TARGETS = cdCommands
before the include for RULES.ioc line.
Remove the lines
ld < seq ld < iocCore
Change "ld < <libname>Lib" to "ld < <libname>.munch"
Change "cd appbin" to "cd topbin"
Change the statement:
dbLoadDatabase("../../dbd/<name>App.dbd")
dbLoadDatabase("../../dbd/<name>.dbd") <name>_registerRecordDeviceDriver(pdbbase)
where <name> is replaced with the name of your dbd file.
If any source file makes calls to recGbl routines make sure it has "#include "recGbl.h". If it doesn't the compiler will issue warning messages and the ioc may issue the message: "undefined symbol: _recGblSetSevr".
The steppermotor, scan, and pid records are no longer in base. If these records are not used in your application, comment out references to them in base.dbd. If these record types are used at your site, they should be downloaded and built with base R3.14 by your EPICS administrator. To update the R3.14 location of these record types in your application you must add appropriate module definitions to your application's config/RELEASE file and add LIBOBJS definitions to the src Makefile.
For example add
PID=<full path to modules directory>/pid
to config/RELEASE and add
LIBOBJS += $(PID_BIN)/pidRecord.oto your application src/Makefile.
You should consider changing any existing old steppermotor records to the new EPICS motor record module supported by Beamline Controls and Data Acquisition at APS.
recDynLink.o and devPtSoft.o are no longer in EPICS base and now exist as separate EPICS modules.You must now add the appropriate module full path definitions to your application config/RELEASE file, and change LIBOBJS location definition $(EPICS_BASE_BIN) to the module definition bin directory in your application src directory files. See "Hardware support changes" below for instructions.
All hardware support (dev, drv and dbd files) except soft support has been unbundled from base R3.14. This support includes the files symb.dbd, drvHp1404a.o, drvEpvxiMsg.o, and drvEpvxi.o. If these are not used by your application, comment out references to them in base.dbd.
Hardware support now exists as separate EPICS modules. The hardware support for your site should be downloaded and built with base R3.14 by your EPICS administrator. You must now add the appropriate module full path definitions to your application config/RELEASE file, and change LIBOBJS location from $(EPICS_BASE_BIN) to the module bin directory in your application src directory files.
For example, remove
LIBOBJS+=$(EPICS_BASE_BIN)/symb
from baseLIBOBJS and add
LIBOBJS+=$(SYMB_BIN)/symb
to your application src/Makefile,
and add the line
SYMB=<full path definition for the built module SYMB>
into your application config/RELEASE file .
The host tool dbLoadTemplate has been replace by a new EPICS extension, msi, which should be downloaded and built with base R3.14 by your EPICS administrator. dbLoadTemplate is still supported on iocs. If, in your application, db files are created from template and substitution files you should add the definition
MSI=<full path name to msi executable>
to your application config/RELEASE file.