Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
<== Date ==> <== Thread ==>

Subject: Re: EPICS 7.0.1-pre1 -- vxWorks 6.2
From: Dirk Zimoch <dirk.zimoch@psi.ch>
To: <core-talk@aps.anl.gov>
Date: Thu, 30 Nov 2017 09:35:54 +0100


On 29.11.2017 21:55, Ralph Lange wrote:
There is a somewhat clumsy manual option.

The modules subdirectory in the new structure is a drop-in place.
If you clone core (without --recursive) and then manually check out only
the submodules you want to build, the build does not need to be
re-configured: it will always build all checked-out submodules. You can
still develop, branch, merge in such a sparse source structure.
It's certainly not automatically by target, but you might be able to get
by with creating two workspaces: complete and classic. Each one would
have the appropriate target configurations: those that can build
everything or those that just support the minimal base.

Cheers,
~Ralph

This is not satisfactory. It should be possible to build all architectures from one checkout.



On Wed, Nov 29, 2017 at 8:47 PM, Andrew Johnson <anj@aps.anl.gov
<mailto:anj@aps.anl.gov>> wrote:

    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



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
Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Ralph Lange

Navigate by Date:
Prev: Jenkins build is back to stable : epics-master » mac #27 APS Jenkins
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  <2017
Navigate by Thread:
Prev: Re: EPICS 7.0.1-pre1 -- vxWorks 6.2 Ralph Lange
Next: RE: EPICS 7.0.1-pre1 -- vxWorks 6.2 Mark Rivers
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
ANJ, 30 Nov 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·