The files that are useful for an application of the command interpreter are the library itself and the file interp.h which should be included by each source file where functions of the library are used. Recall that there are 4 versions of the library : dynamic or static, with or without thread support. One or several initialization files must also be written for each application. The names of the built-in commands must not be put in an initialization file, they are already known by the interpreter. The user is concerned only by the new commands of the application.
If interpcom has been build with command line editing support, the appropriate librairies must be linked with the user object files and the interpcom library to produce the final executable, i.e on Unix
gcc _my_object_files -linter -lreadline -lhistory -ltermcap -lm -o my_program
if GNU readline library is used,
gcc _my_object_files -linter -ltecla -lm -o my_program
if ltecla is, or
gcc _my_object_files -linter -lm -o my_program
if no command line editing library is used (if interpcom library with no thread support is used, take -linter_nothr instead of -linter). On BeOS, -lm should be omitted.