Re: NT changes for 3.12.2

[hill@luke.atdiv.lanl.gov (Jeff Hill)]

> How do VMS and NT cope with blderrSymTbl, which does something very similar to make 
> errSymTbl.c?
> 

I see no problem with fetching errSymTbl.c and envData.c from O.sun4 etc if this
is ok with the VMS and NT users. It would be better if the arch specific
source code was in S.xxxx? Architecture independent source code created by build 
tools should be in S.build? This would make it easier to write tar scripts that 
grab the source and none of the executables/object files.

I just looked in BUILD_VMS.COM and it isnt currently loading errSymTable.o.
It is surprising that we get away with this seeing as many codes in libCom are
using EPICS status (even if the ca client lib isnt for historical reasons).

> How much of base do these CA-only clients actually use 

CA clients now use base/include base/ca and almost all of base/libCom.

> could we have a top level 
> Make target (to be run on a Unix system) which extracts the parts of source tree 
> for a particular non-Unix host architecture and runs any shell scripts required?  
> There are some notes at the top of the BUILD_VMS.COM script which indicate that 
> some automation of this kind could be helpful for the VMS target at least.
> 

This sounds interesting. Perhaps we need an install VMS and an install MS 
windows which would FTP the necessary source onto VMS/NT hosts specified in the 
config area.

Jeff


______________________________________________________________________
Jeffrey O. Hill			Internet	johill@lanl.gov
LANL MS H820			Voice		505 665 1831
Los Alamos, NM 87545 USA 	FAX		505 665 5107