f04f17f9bf
It isn't needed, and in some configurations it causes build failures. Similar problems could still occur for other file types with a similar vpath, but it's less likely that other file types would be installed in an equivalent $(TOP)/../<dir> path. The original issue with .pl files was caused by an installation of Base where the parent directory had a bin/<host> soft-link pointing to the same bin/<host> of a newer installation of the same version of Base, so it had all the necessary .pl files in it. The vpath allowed the build in src/tools to search $(TOP)/../bin/<host> when checking the buildInstall dependency, and since it found those .pl files through the vpath it didn't bother to install them. When they were run later on in the build from the $(TOP)/bin/<host>/ path they weren't present so it failed.
--------------------------------------------------------- EPICS Base - the central core of a control system toolkit --------------------------------------------------------- Copyright (c) 1991-2003 The University of Chicago, as Operator of Argonne National Laboratory. Copyright (c) 1991-2003 The Regents of the University of California, as Operator of Los Alamos National Laboratory. EPICS Base Versions 3.13.7 and higher are distributed subject to a Software License Agreement found in the file LICENSE that is included with this distribution. --------------------------------------------------------- Installation and release information can be found in the various files in the documentation subdirectory. Additional information about EPICS including mailing list archives and subscription instructions, documentation and training materials, additional components, links to other websites etc. is available on the EPICS home page at http://www.aps.anl.gov/epics/