Re: EPICS Application Package

[Jeong Han Lee <citadel.lee@gmail.com>]

Hi,

  Quite interesting discussion, because ESS mentioned several times here.

  I am busy these days, so I cannot reply in detail what we are doing 
here. But if one would like to see what ESS is doing as follows:
  * https://github.com/icshwi/e3          (development)
  * https://github.com/icshwi/e3-builder  (production)

  Someday later, if I can, I will present e3 (ESS EPICS environmet) in 
EPICS collaboration meeting. I hope I could do this in next spring meeting.
  If one would like to copy the entire standard epics, I would like to 
look at the following repo:
  https://github.com/jeonghanlee/epics_builder

  However, it is not for the "production", but for the "personal usage".

  HTH,
  Han



On 10/12/18 8:55 PM, Johnson, Andrew N. wrote:
> On 10/12/2018 01:06 PM, Hinko Kocevar wrote:
> > To avoid hand editing the RELEASE files each time I have an IOC to
> > build, I've coded a python script that takes a 'recipe' for
> > base/module/IOC containing some meta data, including top package
> > dependencies, and delivers a set of built packages - found while
> > resolving deps at compile time.
> There is a tool called Sumo (or EPICS-sumo) that was developed for BESSY
> and published by HZB which automates the process of generating RELEASE
> files and building dependent modules automatically. It takes a bit of
> work to get started with it, but it seems to work very well and I am
> proposing this as the basis for the APS Upgrade's IOC builds.
>
>      http://epics-sumo.sourceforge.net/index.html
>
> There are a number of enhancements that could be added by the community
> including adding a GUI for easy module configuration changes.
>
> - Andrew