Space Science Centre,
School of Engineering & Information Technology,
University of Sussex,
Falmer, Brighton,
East Sussex,
BN1 9QT.
U.K.
DOCUMENT STATUS SHEET
DOCUMENT STATUS SHEET
1.DOCUMENT TITLE: CL-WEC-TED-0514
2. ISSUE
3. REVISION
4. DATE
5. REASON FOR CHANGE
1
1
Sep 01/2001
First Issue.
Prepared by: CLUSTER WEC EGSE
1.Running the package under SunOS 5.7
If you're running the package under SunOS 5.7 (Solaris 2.7) then you can use
the supplied executables and dynamic link library.
bin/levelone
bin/tmc
bin/dumpone
bin/hkm
lib/libted.so
dynamic link library
The executables are all linked ready to use the dynamic link library. The
absolute pathname containing libted.so should be included in the
LD_LIBRARY_PATH environment variable before the executable is run.
A manual page for each of the applications is supplied in the directory man/.
2.Running the package under a different platform
If you're running on a different platform, you'll need to compile the
applications yourself. The source files for the applications are in
src/levelone/
src/tmc/
src/sistodds/
src/dumpone/
src/hkm/
src/lib/
There are Makefiles in each directory that will compile the
application ready to use the dynamic link library lib/ted.so.
You'll probably need to edit the Makefile so it works on your
own machine, especially if you're not using dynamic link libraries.
The "install" target copies the executable files into
bin/.
The source for the TED library is in
src/lib/.
There is a Makefile in src/lib that will build a dynamic
link library and a static library. Again, you'll probably need to
edit the Makefile so it works on your machine. The "install" target
copies the two library files into lib/.
Once you have compiled the package on your machine, we suggest you test it
using a sample set LV0 files available from on-ine data, or from the
CDROM distributed data, where known events occur. Please report any
Bugs through the Anomally reporting system, provided at DRAL (see the
Contact details in the README).
3.Using the TED library for your own application software
As well as the dynamic or static libraries mentioned above, you'll
need the files in include/.
You must always include ted.h before any of the other
files. The file tedsys.h is used by some of the other header
files to access standard libraries. You don't need to include this
file in your own application, but you may need to edit the file so
it works on your machine.
Note that the header files are duplicated in src/lib/. Recompiling the
library transferes a copy of these files in the user include area.
There are other header files in src/lib; you should NOT use these
header files in your own applications as they are not documented in
this release and are NOT included in the interface to the package.
The LEVELONE source file, src/levelone/main.c, is intended to serve as an
example of how applications can be written using the TED Library.