Re: enable pvAccess by default

[William Kirstaedter via Tech-talk <tech-talk at aps.anl.gov>]

Thanks for discussing this.

Are there any public examples / best practices on how to create templates for makeBaseApp?

I'd be interested in creating some for our facility since we end up using asyn, calc, streamdevice alot...

Unrelated, but I also wanted to thank you for introducing the RELEASE.local above $(top) concept a couple years back, since that really made things alot easier! ;)

Thanks @all for your input,
William

Am 3. April 2024 10:29:25 MESZ schrieb Han Lee via Tech-talk <tech-talk at aps.anl.gov>:

I added this subject into an agenda for the upcoming Coderaton at BNL.

BTW, we (ALS-U) use our own template folder to generate our consistent IOC and application directory structure with additional scripts. That is the exact same workflow, which Ralph suggested.

However, from my view, we can just redesign (add a few lines, and change variables a bit) templates/makeBaseApp/top/iocApp/src/Makefile and iocBoot/st.cmd@Cross and st.cmd@common to support pvaccess easily.

Best,

Han

On Wed, Apr 3, 2024 at 12:30 AM Ralph Lange via Tech-talk <tech-talk at aps.anl.gov> wrote:

Note that the template mechanism for makeBaseApp is specifically designed for users to add their own templates.

If you have five things you always need to add to the ioc template, create your own, starting from a copy of the ioc template. Most of the EPICS facilities I know and worked with have their own set of templates.

Cheers,
~Ralph