Re: Build Question

[Dirk Zimoch <dirk.zimoch@psi.ch>]

Hi David,

We have the sources in CVS. Whenever we build something (base or drivers), we 
check out what we need to our home directory and build it locally. Then the O.* 
directories are local which does not matter because they keep only temporary 
files. I have set INSTALL_LOCATION so that the base and driver libraries and 
headers are installed to a central place. Actually, I build base only once where 
the install location is writable. "Normal" development systems for drivers and 
IOCs see a read-only installation of base. Originally we did that with NFS but 
run into some problems when installing new (host) libraries while the same 
library is in use on an other NFS client. We changed to a system where base is 
locally installed from a tar or rpm.

We also keep the driver libraries and headers in a central place. But for 
drivers I use a completely different build system because I have to build the 
drivers not only for different architectures in parallel but even for three 
different EPICS base versions (3.13.9, 3.13.10 and 3.14.8). The EPICS build 
system was not designed for this.

Dirk


David Dudley wrote:
> Is there a way to setup the build system so that the
> O.<$EPICS_HOST_ARCH> directories are in another location?
>
> I'm building for 3 different architectures, and I'd like to put the
> EPICS source on a single (hopefully!) write protected NFS server, and
> link to it when I need access to build, but would rather not have the
> client machine writing directories on the server if I can get away with
> it.
>
> David
>
>
> ------------------------------------------------------------------------
>
> BEGIN:VCARD
> VERSION:2.1
> X-GWTYPE:USER
> FN:David Dudley
> TEL;WORK:880-3740
> ORG:;MIS
> TEL;PREF;FAX:880-3741
> EMAIL;WORK;PREF;NGW:DavidDu@cctexas.com
> N:Dudley;David
> END:VCARD

--
Dr. Dirk Zimoch
Paul Scherrer Institut, WBGB/006
5232 Villigen PSI, Switzerland
Phone +41 56 310 5182