convertRelease didn't resolve paths with ../ in it

[Helge Brands]

perl ../../../../base-3.14.12.2/bin/win32-x86/convertRelease.pl checkRelease

Definition of EPICS_BASE conflicts with PVDATA support.
In this application a RELEASE file defines
        EPICS_BASE = /cygdrive/c/epics/EPICSv4-1.0.1-BETA/pvAccessCPP/../../base-3.14.12.2
but PVDATA at /cygdrive/c/epics/EPICSv4-1.0.1-BETA/pvAccessCPP/../pvDataCPP defines
        EPICS_BASE = /cygdrive/c/epics/base-3.14.12.2

My workaround is to change the RULES_BUILD:

checkRelease:
 -$(CONVERTRELEASE) checkRelease

to avoid cancelation of the build.

[Andrew Johnson (anj)]

Hi Helge,

I will look at this issue, although I can't promise that it can easily be fixed. Since there might be soft-links in the path it is not always correct to replace a/b/../c with a/c — if b is a soft-link to a different part of the tree then a/b/.. is not the same as a, and the directory a/c might not exist or might contain something completely different than a/b/../c.

I recommend using something like the following approach instead if you want to reduce duplication in the file:

SUPPORT = /cygdrive/c/epics
EPICS_BASE = $(SUPPORT)/base-3.14.12.2
EPICS_V4 = $(SUPPORT)/EPICSv4-1.0.1-BETA
PVDATA = $(EPICS_V4)/pvDataCPP
PVACCESS = $(EPICS_V4)/pvAccessCPP

There is also a better workaround than modifying your RULES_BUILD file: Just edit the configure/CONFIG_SITE file in your application and change the CHECK_RELEASE setting from YES to WARN. This will still print the warning but will not stop the build from continuing.

- Andrew

[Andrew Johnson (anj)]

Workarounds available, not worth trying to fix.