Experimental Physics and
Industrial Control System

[email protected] (Michael Bordua) · Tue, 13 Jun 95 15:18:16 PDT

What Janet is proposing looks OK except that not all sites install
their extensions in /usr/local/"whatever", or use the script that APS
does.  Some sites build the extensions alongside base and then use an
extension link in their boot directory just like the base link.  THe
reason for this is that an IOC and/or sub project can be on a different
release of EPICS and still work.  For example, here at LBL we have
projects running on R3.7, R3.11, and at one project both R3.11 and
R3.12Beta.  If the EPICS extensions were in /usr/local or some other
global place then it would be harder for application developers that
have to move across projects to be setup correctly.

What might be a better idea is to have 2 different environment scripts
that could be used.  One sets up for /usr/local (or other global path),
the other sets up for a path the same as base.

One script would do this:

	./base/bin/$HOST_ARCH
	./base/tools
	/usr/local/epics/extensions/bin/$HOST_ARCH

The other script would do this:

	./base/bin/$HOST_ARCH
	./base/tools
	./extensions/bin/$HOST_ARCH

Or we could just let the Site pick their method of making sure
$HOST_ARCH got set correctly.

Mike B.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System