-
Notifications
You must be signed in to change notification settings - Fork 0
/
make.note
81 lines (47 loc) · 1.73 KB
/
make.note
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
Giferator build/install notes
=============================
0. Setup
--------
export PREFIX= place where you'd like to have the software installed,
a lib/idl, lib/sparcv9, or lib64 directory will be created
under here.
export IDL_BIN= path to idl version to build against
/local/bin/idl_5.3 is known to work on solaris 10
export DAS_DATASETROOT= your prefered DSDF location
/usr/local/share/das1 is a reasonable choice
export DAS_TEMP= your prefered log file location
/tmp is what is usually used
1. Build/Install/Test
---------------------
build:
gmake
install:
gmake install
test:
gmake test
kview build*/*.gif
would have been nice for test to work without install but there's no
way that i've found , short of making a *.dlm file for the c-extension
to allow the software to run properly out of the build directory and
still work okay in the install directory.
2. Usage
--------
To use the giferator:
A. Set the IDL_PATH
B. Cat commands to idl
C. rename batch.gif to what you'd like it to be.
A. Set IDL_PATH
One tricky of using the giferator on the command line is figuring
out what the IDL_PATH environment variable sould be. For 32-bit IDL 5.3
this is:
$PREFIX/lib/idl5.3/giferator
For 64-bit IDL 8.2 on linux this is:
$PREFIX/lib64/idl8.1/giferator
What ever that is, lets call it the "giferator_path". The Cassini
environment setup defines RPWS_IDL_PATH. This variable doesn't include
the module name so here's an example usage:
export IDL_PATH="<IDL_DEFAULT>:${RPWS_IDL_PATH}/giferator"
The <IDL_DEFAULT> above is a literal string, it's used by idl to add in it's
default loadable module directory.
B. Cat commands
cat YOUR_CMD_FILE | $(RPWS_IDL)