NDPluginPvxs fails in the constructor if the application is built with both WITH_PVA=YES and WITH_PVXS=YES

[MarkRivers]

The NDPluginPVXS constructor fails if the IOC is built with both WITH_PVA=YES and WITH_PVXS=YES. The constructor fails when this line is present:

      m_record(NTNDArrayRecordPvxs::create(pvName))

The main body of the constructor is never entered, and the destructor for NDPluginDriver is called.

If that line is commented out then the constructor is entered, but of course the plugin does not work.

If the driver is built with WITH_PVA=NO then this problem does not occur.

[MarkRivers]

@mdavidsaver pointed out that this issue is because there are 2 conflicting versions of qsrv.

I was able to build a working IOC that supports both PVA and PVXS by putting these lines in areaDetector/configure/CONFIG_SITE.local. WITH_QSRV=YES must be commented out.

WITH_PVA=YES
WITH_PVXS=YES
#WITH_QSRV=YES

With this configuration I can switch between PVA and PVXS by commenting one or the other following lines in commonPlugins.cmd

#NDPvaConfigure("PVA1", $(QSIZE), 0, "$(PORT)", 0, $(PREFIX)Pva1:Image, 0, 0, 0)
NDPvxsConfigure("PVA1", $(QSIZE), 0, "$(PORT)", 0, $(PREFIX)Pva1:Image, 0, 0, 0)

[MarkRivers]

I am closing this issue since the problem is understood and solved.