README.vms
1 23-DEC-1994
2
3 First, read the various INSTALL and README files for the Unix
4 version of XV as well as these. You can ignore the Unix specific
5 comments, but there are references to the config.h file for local
6 configurations and general use of the program that are relevant to
7 VMS users as well.
8
9 Release notes for building XV (v3.10) on a VMS platform. This
10 includes the newer ALPHA/VMS machines. As in the previous release,
11 it is no longer necessary to apply any patches, etc. to the
12 original Unix code from John Bradley (thanks John!!!). All that is
13 needed is to copy all of the files in this (the [.VMS])
14 sub-directory to the main XV directory This will give you two
15 methods of building the XV package: a DCL command procedure and a
16 MMS description file.
17
18The installation instructions are at the bottom of this file. PLEASE READ!
19
20 MAKE_*.COM
21 These command procedures are a "poor-person's" version of MMS.
22 PLEASE NOTE: You should look through the command procedure to
23 see if any customizing is necessary before executing it! If you
24 have MMS you WILL want to use that method instead.
25
26 SETUP.COM
27 A simple command procedure to setup the final compiled XV
28 package of programs. It helps the aux programs of XV be found
29 by DCL foreign symbols. If you don't want to use the names I
30 have chosen for them, you should be able to alter the CONFIG.H
31 file to point to the names you want to use instead. This has
32 not been tested by me, so let me know if you try this. It
33 should work! :) It can be executed by itself or used with many
34 of the commonly available SETUP packages (i.e., the FERMILAB
35 version). If it is kept in the same directory as the binaries,
36 it will be able to get the necessary symbols setup anywhere the
37 directory structure is located WITHOUT the need to edit the
38 command procedure. Move them all around together and you will
39 be OK.
40
41 MAKEFILE.MMS (in the top level directory)
42 This is a description file for the VMS MMS (or the PD MMK)
43 utility. YOU SHOULD BROWSE THE FILE FIRST TO MAKE SURE THE
44 CUSTOMIZING FEATURES ARE APPROPRIATE FOR YOUR SYSTEM. For users
45 without MMS (MMK) you will need to use MAKE_XV.COM instead.
46
47Installation Instructions:
48
49 Step 0:
50 You need to have installed the DECWindows programmer kit
51 with the C language file selected. You need a C compiler
52 compatible with the VAX C or DEC C installed as well, including
53 the .h files in Sys$Library.
54
55 NOTE: It has been reported that the VAX C v2.4
56 compiler will not work with XV. A reason is not
57 available. Personal experience only extends to VAX C
58 (v3.2-044) and DEC C (v4.0-000) for both Alpha and
59 VAX.
60
61 There are also *rumors* that it will build with the VMS GCC
62 compilers. If anyone has experience in these regards, please
63 send me some info!
64
65 Step 1:
66 The first step in getting XV (v3.10) running on your VMS
67 system is to get the Unix source files on your disk in the
68 structure intended by the Unix environment. This should be like
69 the following:
70
71 [XV-3_10]---+---[.BITS]
72 |
73 +---[.DOCS]
74 |
75 +---[.JPEG]
76 |
77 +---[.TIFF]
78 |
79 +---[.UNSUPT]
80 |
81 +---.[VMS]
82
83 The original Unix compressed tar file can be obtained from
84 ftp.cis.upenn.edu (make sure you get version 3.10!). If you
85 don't have the tools to decompress/detar it, you will need to
86 ask around at various VMS specific Anomymous FTP sites. I would
87 suggest looking first at ftp.spc.edu, cerritos.edu or
88 acfcluster.nyu.edu
89
90 One note for some VAX/VMS systems. The default XV image
91 file (xvdflt.h) has very long lines and may have an error when
92 it is included on the compile step. To fix this, convert the
93 file from it's (probable) STREAM_LF format to a variable length
94 "text" file. This may be as easy as reading in with a "good"
95 editor and simply exiting. Any fail-proof suggestions are
96 welcomed. If you can't get this changed, change the config.h
97 define for the "USEOLDPIC" to be true.
98
99Step 2:
100 You are now ready to build the code. IF you DON'T have MMS,
101 go to Step 3.
102
103 Since you have MMS, you should look through the MAKEFILE.MMS
104 and the appropriate *_Options.OPT files to check for any local
105 customizing changes. XUI vs. MOTIF is an issue you will have
106 to resolve first!!! Note specifically the references to JPEG
107 and TIFF. This is also true for the MAKEFILE.MMS in the JPEG
108 sub-directory and the MAKEFILE.MMS file in the TIFF
109 sub-directory.
110
111 EXCEPT for the destination of the binaries, and X11 Window
112 interface, I *think* it should work for everyone without any
113 modifications. (famous last words...)
114
115 When you are satisfied that everything is correct for your
116 site, just type
117
118 MMS /Description = MAKEFILE.MMS
119
120 if you have a traditional VAX with VAX C. If you have
121 traditional VAX with DEC C (v4.0-000) then type
122
123 MMS /Description = MAKEFILE.MMS /Macro = (DECC=1)
124
125 or if you have an Alpha with DEC C (v4.0-000), type
126
127 MMS /Description = MAKEFILE.MMS /Macro = (Alpha=1)
128
129 Any of these commands may need the DEC_XUI=1 macro as well. If
130 you don't have MOTIF, you should add it. Now just sit back and
131 watch XV being built. This may take quite a while depending on
132 your system's speed/load. It may also require that your system
133 have it's virtual memory increased. If you get an error message
134 of this type, see a system guru for help! If it occurs, it will
135 probably happen with the TIFF code for FAX support. You can
136 always undefine the HAVE_TIFF symbol in the top Makefile and
137 dump the TIFF support.
138
139 When you are successfully finished, go to Step 4.
140
141 Step 3:
142 If you don't have MMS you will need to execute the supplied
143 command procedure to build the XV package. You should look
144 through the MAKE_XV.COM file to check for any customizing
145 changes. Note specifically the references to JPEG, and TIFF.
146
147 When you are satisfied that your site changes are correct,
148 execute the MAKE_XV.COM and watch it build the package. If
149 there are any problems you will want to delete the offending
150 .OBJ file so the command procedure will try to build it again
151 instead of skipping to the next one. This stuff is trickier to
152 'restart' it, so be careful if you need do.
153
154 Step 4:
155 If there were no errors, you should be finished and would
156 just need to execute SETUP.COM to start viewing images!!! If
157 you want to use GUnZip, make sure it is available as well. It
158 is referenced via the UnCompress.com procedure.
159
160 Step 5:
161 Send John Bradley a short note telling him you love his XV
162 program on VMS machines. The VMS part is crucial! :) We should
163 all thank him for including the VMS support in XV
164 'out-of-the-box'! I would also encourge you to send in the
165 registration amounts if they are appropriate to your suggestion.
166 This program is one hell of a lot of work...
167
168 Step 6:
169 There are two environment (logical) names that the VMS
170 version of XV uses. One is XV_Root_Device which helps move
171 across VMS devices like the Unix FileSystem does naturally. It
172 is just a little hack that is provided with no support. :) The
173 other one is XV_Queue which should point to a PostScript print
174 queue if you have GhostScript installed and defined in the
175 config.h file.
176
177 Step 7:
178 IF you had any problems or just want to make a comment about
179 my installation instructions or VMS port, please send me e-mail
180 at any of the addresses below.
181
182--
183Richard L. Dyson INTERNET: Dyson@IowaSP.Physics.UIowa.EDU
184 _ _ _____ Senior Programmer Analyst O: 319/335-1879
185| | | | |_ _| Department of Physics & Astronomy H: 319/338-6117
186| | | | of | | Van Allen Hall FAX: 319/335-1753
187| \_/ | _| |_ University of Iowa NSI/DECnet: IOWASP::DYSON
188 \___/ |_____| Iowa City, IA 52242-1479 or : 7231::DYSON
189