EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: ioc startup file installation
From: Felix Krämer via Tech-talk <tech-talk at aps.anl.gov>
To: tech-talk at aps.anl.gov
Date: Fri, 27 Nov 2020 14:17:11 +0100
Hi all,

Currently, I do some contractor work for Gemini for a new Application Development Environment based on RPM.

In this context, I am working on one part of it to provide a framwork for softIOC installation, everything readily set up with conserver configuration, procServ etc. after installing a respective softIOC RPM. I do this development work based on a makeBaseApp.pl generated softIOC example from the EPICS Application Developer's Guide ( https://epics.anl.gov/base/R3-15/6-docs/AppDevGuide/GettingStarted.html#x3-60002.2 ). For installing EPICS software using RPM we have to _relocate_ installed binaries, scripts etc. This works well, principally, but regarding the example softIOC there do arise a few questions:

(1) The startup file under iocBoot (st.cmd) is not installed anywhere. If INSTALL_LOCATION is not redefined, then this is not a problem, but if I want to keep the sources distinct from the product, this seems not to be consequent. I patched the Makefile from

TOP = ../..
include $(TOP)/configure/CONFIG
ARCH = $(EPICS_HOST_ARCH)
TARGETS = envPaths
include $(TOP)/configure/RULES.ioc


to

TOP = ../..
include $(TOP)/configure/CONFIG
ARCH = $(EPICS_HOST_ARCH)
TARGETS = envPaths
SCRIPTS_IOC_Linux += st.cmd
include $(TOP)/configure/RULES.ioc
include $(TOP)/configure/RULES

to install the st.cmd to the binary install dir, at least. In the %post section of the RPM specfile (which is called after installing an RPM) I could then call convertRelease.pl again to let envPaths look like it should. Is this the way to go? Or is there a better way (I believe I remember sth like directories named 'startup' or so in the past, but maybe this was Gemini-specific)

(2) Another option I thought about would be to define a User Created File type ( https://epics.anl.gov/base/R3-15/6-docs/AppDevGuide/BuildFacility.html#x5-1570004.6.35 ), e.g. a FILE_TYPE IOCBOOT which would install this st.cmd to a INSTALL_IOCBOOT = $(INSTALL_LOCATION)/iocBoot/.... directory, for example.

Or do I think completely in the wrong direction and there is already a mechanism in place which I simply do not see?

Any help or ideas appreciated.

Thanks,
Felix

Replies:
ioc startup files not installed to INSTALL_LOCATION Felix Krämer via Tech-talk

Navigate by Date:
Prev: RE:Alarm indicator in CSS Donny Domagoj Cosic via Tech-talk
Next: RE:RE:Alarm indicator in CSS GAGET Alexis via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: RE:RE:Alarm indicator in CSS Donny Domagoj Cosic via Tech-talk
Next: ioc startup files not installed to INSTALL_LOCATION Felix Krämer via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
ANJ, 14 Dec 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·