-
Notifications
You must be signed in to change notification settings - Fork 5
/
Copy pathREADME.NT
71 lines (46 loc) · 2.07 KB
/
README.NT
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
Eddie 1.4.2 Note:
Windows NT does not work, but it's not that far away.
You'll need to get the relay code in inet_server/c_src working and get
the script stuff in oam/src/*.src working under bash under windows.
The gateway stuff is pretty much useful because Cygwin select() is
really slow. inet_server/c_src code probably should be rewritten
using io ports under NT.
The rest of this document is now out of date but may give
you some useful pointers.
Software requirements
~~~~~~~~~~~~~~~~~~~~~
1. Cygwin tools from http://sourceware.cygnus.com/cygwin.
Eddie was tested with cygwin B20.1 successfully.
2. GNU autoconf from ftp://prep.ai.mit.edu/pub/gnu/autoconf (or mirror site).
It should compile out of the box using Cygwin tools.
Eddie was tested with autoconf 2.13 successfully.
3. Microsoft Visual C++ v4.0 or newer.
This compiler is required for Windows NT system-level programs.
4. Open Source Erlang from http://www.erlang.org.
Installation
~~~~~~~~~~~~
0. Run the bash shell from cygwin and use that as the installation
environment.
1. Make sure you have Open Source Erlang installed
(http://www.erlang.org).
Ensure "erl" & "erlc" are in your standard path.
2. Unpack this(!) source where you want all the Erlang binaries
to reside.
3. sh configure
4. make
5. make install
This should build Eddie succsessfully. Getting Eddie
running requires an understanding of how your want to configure
your cluster(s). Please read the documentation in the doc/ subtrees.
Put $EDDIE_ROOT/bin in your path!
This process needs to be repeated for each machine you
install Eddie on.
Notes
~~~~~
1. The Bourne shell that comes with Cygwin does not have features
such as getopt. Run the eddie script
with the bash shell (i.e. bash eddie init -c Cookie -d d:/database ....)..
2. IP migration is not available for Windows NT. NT does not have
a means for adding/removing IP aliases without rebooting. Consequently,
the "AutoConfig" directives in the configuration files must be set to
"Off", otherwise, a runtime error will result.