EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Redundancy Patch: makeBaseApp
From: "Liu, Gongfa" <[email protected]>
To: EPICS core-talk <[email protected]>
Date: Mon, 19 Nov 2007 17:28:18 +0100
Hi, Andrew,

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.

Yes, you are right. It does not cover the case without an entry for SNCSEQ. The original purpose is that it is convenient for redundancy users. The modification can be ignored if it confuses non-redundancy beginners.

Bernd Schoeneburg and Gongfa Liu
--
----------------------------------------------------------
Gongfa Liu                         MKS-2, DESY
phone:  +49-40-8998-1642           Notkestr. 85
fax:    +49-40-8998-4388           22607 Hamburg
e-mail: [email protected]         Germany
----------------------------------------------------------

References:
Redundancy Patch: makeBaseApp Andrew Johnson
Re: Redundancy Patch: makeBaseApp Andrew Johnson

Navigate by Date:
Prev: Re: Redundancy Patch: iocsh Liu, Gongfa
Next: Re: Redundancy Patch: iocsh Andrew Johnson
Index: 2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Redundancy Patch: makeBaseApp Andrew Johnson
Next: [Fwd: Re: Timing/Event Systems] Andrew Johnson
Index: 2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·