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  <20182019  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  <20182019 
<== Date ==> <== Thread ==>

Subject: Re: EPICS Application Package
From: "Vishnu Patel" <vishnu.patel@rediffmail.com>
To: "Ralph Lange" <ralph.lange@gmx.de>
Cc: EPICS Tech Talk <tech-talk@aps.anl.gov>
Date: 15 Oct 2018 14:45:02 -0000
Once for Windows host, I used to copy library files from epics/bin, asyn/bin etc to bin directory of application. Copy the complete application folder to other similar machine, and it's working for me without installing epics, as all library comes in same folder.

I never tried with Linux but it is interesting to package application for deployment host.
- Vishnu

Sent from RediffmailNG on Android




From: Ralph Lange <ralph.lange@gmx.de>
Sent: Fri, 12 Oct 2018 20:42:16 GMT+0530
To: EPICS Tech Talk <tech-talk@aps.anl.gov>
Subject: Re: EPICS Application Package

Hi Bo,

Yes, I was referring to the ESS EPICS setup, which has been developed based on the PSI implementation.
And: no, there is no way to get this working with just a "normal base" system. That run-time module resolution and linking mechanism is a complicated beast, and needs additional tools and services.
Bugs in such setups have the tendency to show up at run time as spontaneous core dumps.

Starting from "normal base", your basic option is shared libraries vs. statically built binaries. When using shared libraries, you have to make sure that the right versions of the right libraries are in the right place when running the IOC. EPICS won't help you with that, so people use package managers or containers to do this.
If you build statically, you can usually get by with tarring up the installation directories of your IOC application, and extracting that archive on the machine that will run the IOC.
That is a lot easier and pretty robust.

Cheers,
~Ralph


On Fri, 12 Oct 2018 at 16:23, Bo Jakobsen <lister@f77.dk> wrote:
Hi

I am also very interested in this thread as I am working on a new setup.
I worked with the below described configuration when working with the ESS EPICS setup, but could you please provide some information on how to do this from the "normal base" epics system. All demos and docs I have seen ends up with compiling the ioc binary including the support libraries in the process.


On 2018-10-12 09:37, Ralph Lange wrote:
Other institutes are using an NFS mounted repository of all applications and shared libraries and a database of versions of tested combinations of these, and load device support and EPICS modules dynamically from the startup script of the IOC. This also needs a careful design and serious building infrastructure in the background, but maybe requires less upfront work and learning compared to the first option.

Best
    Bo


Navigate by Date:
Prev: EPICS driver for ThorLABS MCLS1 Hu, Yong
Next: Re: Controlling Eiger 1M with EPICS Jason A . Pattie
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  <20182019 
Navigate by Thread:
Prev: EPICS driver for ThorLABS MCLS1 Hu, Yong
Next: Camera Recommendations [SEC=UNCLASSIFIED] POZAR, Andraz
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  <20182019 
ANJ, 16 Oct 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·