Hi,
Here at SLAC we organize our RELEASE files with variables for the versions of the modules and after that the path for them, e.g.:
ASYN_MODULE_VERSION=R4.30-0.3.0
CEXP_MODULE_VERSION=R1.0.1
STREAM_MODULE_VERSION=R2.7.7-0.1
YAMLLOADER_VERSION=R1.0.1
ASYN=$(EPICS_MODULES)/asyn/$(ASYN_MODULE_VERSION)
CEXP=$(EPICS_MODULES)/cexpsh/$(CEXP_MODULE_VERSION)
STREAM=$(EPICS_MODULES)/streamdevice/$(STREAM_MODULE_VERSION)
YAMLLOADER=$(EPICS_MODULES)/yamlloader/$(YAMLLOADER_VERSION)
With the migration to R3.15.5 and the change on our tag naming convention we started to see the following error message:
----------------------------
----------------------------
Here are the questions:
- What would be the problem of having more than one variable pointing to the same place?
- Are the order of the includes and linking defined by the other that they appear at the RELEASE file?
We know that there are solutions such as adding the variables immediately above or below the other and also bring the version number to the module path to avoid conflicts but we are curious to understand why.
The additional checks were introduced with this commit:
Thank you,
Hugo