EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: RE: EPICS 7.0.1-pre1 -- vxWorks 6.2
From: Mark Rivers <[email protected]>
To: 'Andrew Johnson' <[email protected]>, "[email protected]" <[email protected]>
Date: Wed, 29 Nov 2017 20:59:53 +0000
> It's even more complicated than that though; once we get Base to only
> build the PVA modules for some target architectures and not for others,
> how are the Makefiles in downstream modules such as AreaDetector
> supposed to be set up to only build things that depend on PVA for
> targets that have PVA built?

areaDetector already handles this.  All of its Makefiles have constructs like this for things that depend on PVA (aka EPICS_V4).

ifeq ($(WITH_EPICS_V4), YES)
  DBD += NDPluginPva.dbd
  INC += NDPluginPva.h
  LIB_SRCS += NDPluginPva.cpp
endif

Of course this brings up my favorite complaint about the fact that dbd files are in O.Common rather than an architecture-specific directory.  We now have to play silly games with naming DBD files differently for each architecture if one supports PVA and another does not.

Mark

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Johnson
Sent: Wednesday, November 29, 2017 1:48 PM
To: [email protected]
Subject: Re: EPICS 7.0.1-pre1 -- vxWorks 6.2

On 11/29/2017 02:07 AM, Dirk Zimoch wrote:
> 
> I will try to implement something. My first attempt failed for the
> reason Andrew outlined. It is not possible to simply skip the all PVA
> modules for a specific T_A because at that time T_A is not yet defined.
> A flag needs to be checked inside every module.

It's even more complicated than that though; once we get Base to only
build the PVA modules for some target architectures and not for others,
how are the Makefiles in downstream modules such as AreaDetector
supposed to be set up to only build things that depend on PVA for
targets that have PVA built?

After thinking this over last night I now think it would be much more
complex and invasive than the original idea appears. It certainly isn't
going to be possible in the 7.0.1 release.

If you want to use EPICS 7, I think you will have to upgrade your
devices to run on a fully supported OS; partial support like this is
likely to be too invasive to be cost-effective.

- Andrew

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon

Replies:
Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Dirk Zimoch
References:
EPICS 7.0.1-pre1 Andrew Johnson
Re: EPICS 7.0.1-pre1 Dirk Zimoch
Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Dirk Zimoch
Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Dirk Zimoch
Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Hartman, Steven M.
Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Timo Korhonen
Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Andrew Johnson
Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Dirk Zimoch
Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Andrew Johnson

Navigate by Date:
Prev: Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Ralph Lange
Next: Re: SIML type CA and PINI=YES issue Andrew Johnson
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Dirk Zimoch
Next: Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Dirk Zimoch
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
ANJ, 21 Dec 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·