Re: asyn: No rule to make target 'ipSNCServer.o'; Does configure/RELEASE have multiple pointers to ...

["Hu, Yong via Tech-talk" <tech-talk at aps.anl.gov>]

Thank you, Mark! It works with empty values. I do not see asyn is trying to build “testIPServerApp” any more.

SUPPORT=

IPAC=

SNCSEQ=

 

 

On 4/21/21, 10:35 AM, "Mark Rivers" <rivers at cars.uchicago.edu> wrote:

 

Hi Yong,

 

• So, my questions: do we really need the following 3 lines in asyn/configure/RELEASE?
• SUPPORT=/corvette/home/epics/devel
• IPAC=$(SUPPORT)/ipac-2-15
• SNCSEQ=$(SUPPORT)/seq-2-2-5

 

Actually asyn configure/RELEASE has explanatory comments before each of those lines:

 

#  IPAC is only necessary if support for Greensprings IP488 is required

#  IPAC release V2-7 or later is required.

IPAC=$(SUPPORT)/ipac-2-15

 

# SEQ is required for testIPServer

SNCSEQ=$(SUPPORT)/seq-2-2-5

 

## For sCalcout support in asynOctet - applications include asynCalc.dbd

#CALC=$(SUPPORT)/calc-3-7-3

 

# If CALC was built with SSCAN support then SSCAN must be defined for testEpicsApp

#SSCAN=$(SUPPORT)/sscan-2-11-3

 

#  EPICS_BASE 3.14.6 or later is required

EPICS_BASE=/corvette/usr/local/epics-devel/base-7.0.4

 

I believe you can achieve what you want without editing RELEASE by putting these lines in RELEASE.local

 

SUPPORT=

IPAC=

SNCSEQ=

 

I think that should work because RELEASE.local is read after RELEASE, and so you will replace those 3 definitions.  I have not tested it, so please try it.

 

Mark