Re: Redundancy Patch: makeBaseApp

[Andrew Johnson <anj@aps.anl.gov>]

Andrew Johnson wrote:
> **************
> Modified
> **************
>
> # source files
> (16) base-3.14.9/src/makeBaseApp/top/configure/RELEASE
>     The following lines are added for supporting iocRedundancy package:
>         #If using iocRedundacy package, point REDUNDANCY at its top 
> directory:
>         #REDUNDANCY=$(EPICS_BASE)/../modules/soft/iocRedundancy
>
> (17) base-3.14.9/src/makeBaseApp/top/exampleApp/src/Makefile
>     The following lines are added for building redundant IOC application:
>         # NOTE: To build redundant IOC application, REDUNDANCY must be 
> defined
>         # in the <top>/configure/RELEASE file
>
>         ifneq ($(REDUNDANCY),)
>            _APPNAME__DBD += rmt.dbd
>            _APPNAME__DBD += cce.dbd
>            _APPNAME__DBD += snlexec.dbd
>            _APPNAME__LIBS += rmt
>            _APPNAME__LIBS += cce
>            _APPNAME__LIBS += snlexec
>         endif

I don't see the need to include links to the redundancy subsystem in the 
makeBaseApp example template; the majority of EPICS users won't be using 
the redundancy system, and I'd prefer not to confuse beginners with 
information that is of no use them (that being the main purpose of the 
makeBaseApp templates).

The additions necessary to create a redundant IOC just need to be 
documented with the redundancy system, which could provide its own 
makeBaseApp templates if it desires (makeBaseApp.pl can be told to look 
in a different location for its templates).

Have you tested building a redundant IOC without an entry for SNCSEQ in 
its configure/RELEASE file?  I suspect the above would not be sufficient 
to cover this case, assuming it is possible to build such an IOC.

- Andrew
--
When a distinguished but elderly scientist states that something is
possible, he is almost certainly right.  When he states that something
is impossible, he is very probably wrong.  -- Arthur C. Clarke