3.1 Configuring Programs to Use OPeNDAP

Relinking an existing program with the OPeNDAP implementation of some data API is a simple procedure. Find the directory that contains the source/object code of the program you want to re-link and modify the makefile (typically called Makefile) for the program so that the OPeNDAP-compliant API library is used in place of the standard API library. (If you can't find the libraries on your system, see Appendix A, or ask the system administrator.) These libraries are:  

libdap++.a

Software common to all of the OPeNDAP-supported APIs.

OPeNDAP also uses facilities from some standard libraries, and these must also be included in the link to resolve all the symbols.

libwww.a

The World Wide Web library. This contains the functions used to communicate between the OPeNDAP client and server.

libexpect.a

Functions from the expect library are used to communicate between OPeNDAP client processes.  

libtcl.a

Contains definitions necessary for the expect library. The use of this library in the link is not related to the use of Tcl by OPeNDAP clients.  

libstdc++.a

The GNU C++ class library (This is not necessary if using g++ to re-link.)  

You will also need to include the library containing the OPeNDAP-compliant version of the API. The name of this library of course depends on the API, but it is generally in the form

lib API-dods.a 

Where API is an abbreviation indicating the API emulated by the specified library. For example, the OPeNDAP-compliant netCDF library is called libnc-dods.a and the JGOFS version is libjg-dods.a.

• 3.1.1 An Example Using netCDF
• 3.1.2 Potential Problems