When SNCSEQ is set in RELEASE, which typically happens when using the include ../../RELEASE.local mechanism, installing into INSTALL_LOCATION fails. The symptom is that RULES_SNCSEQ is installed into the $(INSTALL_LOCATION)/cfg directory, but the build at some point expects to find it in the $(INSTALL_LOCATION)/configure directory.
The cause is a backwards compatibility shim that the sequencer has in RULES_BUILD, which makes it compatible with EPICS base earlier than 3.15. Two solutions were discussed:
- Adding an
ifndef BASE_3_15 guard to RULES_BUILD
- Making
RULES_BUILD a copy of RULES_SNCSEQ
It is not yet clear which approach is better.
When
SNCSEQis set inRELEASE, which typically happens when using theinclude ../../RELEASE.localmechanism, installing intoINSTALL_LOCATIONfails. The symptom is thatRULES_SNCSEQis installed into the$(INSTALL_LOCATION)/cfgdirectory, but the build at some point expects to find it in the$(INSTALL_LOCATION)/configuredirectory.The cause is a backwards compatibility shim that the sequencer has in
RULES_BUILD, which makes it compatible with EPICS base earlier than 3.15. Two solutions were discussed:ifndef BASE_3_15guard toRULES_BUILDRULES_BUILDa copy ofRULES_SNCSEQIt is not yet clear which approach is better.