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  <20122013  2014  2015  2016  2017  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: RE: using areaDetector as a support library only
From: Mark Rivers <rivers@cars.uchicago.edu>
To: "'Ernest L. Williams Jr.'" <ernesto@slac.stanford.edu>
Cc: Tech Talk <tech-talk@aps.anl.gov>
Date: Tue, 15 May 2012 21:54:58 +0000
Hi Ernest,

The next release of areaDetector will be R1-8.  It will keep the same structure as the current release, and should be out soon.  I am making the final tweaks to a driver for the Photonic Sciences Limited detectors.

For the release after that I will break areaDetector into multiple modules.

areaDetector will contain only the code for ADSrc and pluginSrc.  It will not depend on any other EPICS modules besides base and asyn.

Each detector will be in its own module, e.g. ADProsilica or something like that.  My plan was to make ADProsilica build both the library and the example application.  That means its configure/RELEASE would depend on synApps modules like what you show.  You still might not like that, since you would want the ADProsilica module to also be just a library that you can build into your IOC.

I could break each detector into 2 modules:
ADProsilicaLib - just builds a library, does not depend on any other modules except base and asyn
ADProsilicaApp - builds an example application, depends on other synApps modules

The problem with that is that areaDetector would then be broken into 29 modules, since there are currently 14 detectors plus the base code.  That's a lot more work for me, since each needs to be separately packaged and released.  But maybe it's the best way to do it.

I'm also sending this to tech-talk, since I know others have expressed similar desires, and I'd like to get comments.

Mark


From: Ernest L. Williams Jr. [mailto:ernesto@slac.stanford.edu] 
Sent: Tuesday, May 15, 2012 4:32 PM
To: Mark Rivers
Cc: Williams Jr., Ernest L.
Subject: using areaDetector as a support library only

Hi Mark,

In an effort to reduce dependencies when preparing a shared module such as areaDetector; how to do this?

Here is what we have now:
SNCSEQ=$(EPICS_MODULES)/seq/$(SEQ_MODULE_VERSION)
AUTOSAVE=$(EPICS_MODULES)/autosave/$(AUTOSAVE_MODULE_VERSION)
ASYN=$(EPICS_MODULES)/asyn/$(ASYN_MODULE_VERSION)
SSCAN=$(EPICS_MODULES)/sscan/$(SSCAN_MODULE_VERSION)
CALC=$(EPICS_MODULES)/calc/$(CALC_MODULE_VERSION)
BUSY=$(EPICS_MODULES)/busy/$(BUSY_MODULE_VERSION)
STD=$(EPICS_MODULES)/std/$(STD_MODULE_VERSION)
MCA=$(EPICS_MODULES)/mca/$(MCA_MODULE_VERSION)


I would like to build areaDetector as a support library that is referenced and linked in by an
IOC application.

This means that I would like to select not to build the IOC parts of areaDetector as they depend on such as autosave.
What is the best way to achieve this?
Seems that every driver creates an App via  "ADApp/commonDriverMakefile"

I only want to include those components necessary for the module library.
We will include the other components along with our IOC Application.
What is the cleanest way to do this?

Cheers,
Ernest


Replies:
Re: using areaDetector as a support library only Ernest L. Williams Jr.

Navigate by Date:
Prev: EPICS3.14.12 RTEMS patch for nfsMount() ( was Re: Autosave and RTEMS-4.10) Kate Feng
Next: Re: using areaDetector as a support library only Ernest L. Williams Jr.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017 
Navigate by Thread:
Prev: Re: cPCI express Urša Rojec
Next: Re: using areaDetector as a support library only Ernest L. Williams Jr.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·