Install gcc (requires root permissions) if it is not installed already (try the command 'gcc --version' to check).
Install an HTTP client library (optional, requires root permissions) if one is not installed already (try the commands 'curl-config --version' and 'libwww-config --version' to check). If either command works, skip to step 3.
Install the X11 developer's toolkit and XView (optional, requires root permissions) if they are not already installed. (Check for the presence of Xlib.h, which is usually found in /usr/include/X11, to see if the X11 developer's toolkit has been installed. Check for the presence of textedit, which is usually found in /usr/openwin/bin, to see if XView has been installed.)
Download the current version of the WFDB software package as sources or binaries. Binary packages are provided as a convenience and may not be up-to-date; we strongly recommend following the procedure described below for compiling the software from the sources instead. If you plan to compile WFDB applications that are not included in the binary package, please start with the sources.
If you download the sources (recommended):
Unpack the archive of sources:
tar xfvz wfdb.tar.gz
If you don't have GNU tar, you may need to uncompress the archive before unpacking it, like this:
gzip -d wfdb.tar.gz tar xfv wfdb.tar
Unpacking the archive creates a directory with a name of the form wfdb-10.m.n within your working directory.
Enter this directory, configure, and install the package:
cd wfdb-10.m.n ./configure make install
The make command requires root permissions, and installs the package in subdirectories of /usr. If you do not have root permissions, you may install the package in any writable directory by adding an appropriate option to the make command above:
make install WFDBROOT=/path/to/another/directory
Note that in this case you will need to add WFDBROOT/bin to your PATH, and WFDBROOT/lib to your LD_LIBRARY_PATH.
This step compiles a short program that exercises the WFDB library and applications, and prints a summary of test results. The tests are very short (typically less than a second each), except that the last one (xform using NETFILES) may take up to a minute if you have a slow or inoperative Internet connection. If any application test fails, its output (program.out) can be found in the checkpkg subdirectory of the WFDB source tree; compare this output with the file of the same name that can be found in the checkpkg/expected subdirectory.
If you download the binaries (not recommended):
If XView is installed, test WAVE with the command:
wave -r mitdb/200 -a atr
If you have not used WAVE before, you may want to follow through the tutorial material in the beginning of the WAVE User's Guide.
Read the manuals. Really! :-) If you want to write your own software to work with PhysioBank data, begin with the WFDB Programmer's Guide. To learn about the wide variety of existing software that can be used to study PhysioBank data, read the WFDB Applications Guide and the WAVE User's Guide.