Original LaunchPad bug #1461687 reported by Andrew Johnson (@anjohnson) 2015-06-03:
Building a stand-alone (static) gateway without creating any RELEASE.local files [which are good for developers but not for operational installation builds], my build failed under testTop because EPICS_BASE was not set. One of the uncommented lines in the testTop/configure/RELEASE file should be
-include $(GATEWAY)/configure/RELEASE
to get the definition of EPICS_BASE from the parent module.
Thus as with other standard support modules I should only have to edit the top-level configure/RELEASE file and the whole thing should then build successfully.
Does this reorganized gateway still build using the gnuregex extension or an equivalent Linux library? There's nothing in either the RELEASE or CONFIG_SITE files explaining how to configure this. I would expect to see a switch in the CONFIG_SITE file, and maybe another path in the RELEASE file for it; this wasn't previously needed when the EPICS gnuregex extension installed its files into the extensions install directories, but if Linux distributions come with a suitable library already built maybe it's not needed.
Original LaunchPad bug #1461687 reported by Andrew Johnson (@anjohnson) 2015-06-03:
Building a stand-alone (static) gateway without creating any RELEASE.local files [which are good for developers but not for operational installation builds], my build failed under testTop because EPICS_BASE was not set. One of the uncommented lines in the testTop/configure/RELEASE file should be
to get the definition of EPICS_BASE from the parent module.
Thus as with other standard support modules I should only have to edit the top-level configure/RELEASE file and the whole thing should then build successfully.
Does this reorganized gateway still build using the gnuregex extension or an equivalent Linux library? There's nothing in either the RELEASE or CONFIG_SITE files explaining how to configure this. I would expect to see a switch in the CONFIG_SITE file, and maybe another path in the RELEASE file for it; this wasn't previously needed when the EPICS gnuregex extension installed its files into the extensions install directories, but if Linux distributions come with a suitable library already built maybe it's not needed.