Re: Building for more than one host architecture

[watson@cds002.cebaf.gov]

>       1)  The EPICS startup script will add the following directories to
>           a user's path (for application development)
>           
>               ./base/bin/$HOST_ARCH
>               ./base/tools
>               /usr/local/epics/extensions/bin/$HOST_ARCH
 
I'm not fond of installing code in /usr/local.  Assume that EPICS is installed
in the path $EPICS, then add the following to everyone's path:

		$EPICS/base/bin/$HOST_ARCH
		$EPICS/base/tools
		$EPICS/extensions/bin/$HOST_ARCH

At CEBAF we have a "setup" utility that lets us type

		setup epics3_12

and setup finds and sources a .setup file in the directory 

	<site specific search list>/epics3_12

in this file we define version specific environment variables, path, aliases,
etc., including $EPICS.  Our "setup" facility is a bunch of csh scripts and
is available to all.  It also supports recursive setup (i.e. .setup invokes
setup).

Chip