Installing the CWB
As an executable:
- make sure the file is the correct one for your system architecture;
- make the file executable;
If you're content to start the CWB from the directory where the executable
lives, you're done. If (more likely) that directory is in your PATH and you
want to be able to start the CWB from anywhere, sadly there's more to do:
- decide what command you want to use to invoke your executable; say
cwb
- rename the executable file to
cwb.heap2exec
- in the same directory, which is in your path, create an executable
script called
cwb containing the two lines:
#!/usr/local/bin/bash
/full/path/name/cwb.heap2exec $*
(replacing the shell name in the first line by the name of your shell and
putting in the pathname to your executable in the second line)
I don't know what the equivalent of these instructions should be for
non-Unix systems, sorry -- if someone sends them to me I'll add them here.
(Explanation of why
the last 3 steps are necessary)
As a heap image (requires an ML runtime system):
Make sure the heap image itself is the right one for your system
architecture. Then wrap it up in a script that says something like:
your-compiler-name @SMLload=your-heap-image-name
Make sure your script is executable and is in your PATH, as before.
No, I don't know any reason why you'd want a heap image if you could have
an executable instead. But building an executable from a heap image is a
pain, so if you're compiling the CWB yourself you may prefer to stick with
the heap image rather than going to the trouble of building the executable.
Perdita.Stevens@ed.ac.uk