Re: enable pvAccess by default

[Érico Nogueira Rolim via Tech-talk <tech-talk at aps.anl.gov>]

On 31/03/2024 17:53, William Kirstaedter via Tech-talk wrote:
> Hello Core Devs,


Hi!

I'm not a core dev, though ;)


>
> I would like to know if you have already considered activating
> pvAccess for softIOCs by default.
>
> I would probably adapt the Makefile template and simply copy the
> section from the example IOC:
>
> # Link QSRV (pvAccess Server) if available
> ifdef EPICS_QSRV_MAJOR_VERSION
>     _APPNAME__LIBS += qsrv
>     _APPNAME__LIBS += $(EPICS_BASE_PVA_CORE_LIBS)
>     _APPNAME__DBD += PVAServerRegister.dbd
>     _APPNAME__DBD += qsrv.dbd
> endif


It would be good to know the plans for integration of PVXS into
epics-base regarding naming of dbd files and libraries. Are they going
to be changed to match the original names for the PVAccess modules, or
keep the current PVXS ones [1]? If the latter, this change to the
templates would only work for the original names, and would break builds.


I have been thinking instead that it would be nice if we could have a
configure/CONFIG_SITE option in epics-base that includes the current
official PVA server (whatever that is) functions in base.dbd and the PVA
server libraries in EPICS_BASE_IOC_LIBS. That way, sites can enforce
policy for enabling PVA without requiring changes to Makefiles
(especially given that these aren't the Makefiles under configure/, but
the *App/src/Makefile ones, which ideally shouldn't have to be changed
for site-specific builds). This seems like a good opportunity to put
that idea forward :)


[1] https://urldefense.us/v3/__https://mdavidsaver.github.io/pvxs/building.html*includepvxs__;Iw!!G_uCfscf7eWS!e2US3OobS-QtL_mQSkjlE1a0rEchIjYGbsoor4PS4v3fH8-evPo8RMiWXeqb_QP3CY3ScIy6z3m8C9LZPYD9Rl4Fmrs$ 


Cheers,

Érico


>
> Ultimately, this should not affect any old system, as pvAccess is only
> loaded if it is also present in base?
>
> thanks in advance,
>


Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente.

Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately.