Kalotay
Analytics
A Division of Andrew Kalotay Associates, Inc.
BondOAS™ Library Installation

Distribution

The BondOAS™ package is distributed as an archive file. Either a .zip file for Windows or a .tar.gz file for Unix. The archive has a top level directory, akalib/ with sub-directories beneath that. This is strictly an archive file.

akalib/ doc/ csharp/ java/ include/ {operating-system}{architecture}/ lib/ static/

Installation Location

There is no specific requirement for the installation location. The user can un-archive the distribution in any location. We recommended installing the entire package in a system wide location. For Unix we recommend:

/usr/lib/

or

/usr/local/lib/

For Windows we recommend:

Program Files\Andrew Kalotay Associates\

In all cases the akalib directory is a sub-directory of those locations.

You will need to have root or (under Windows) administrative privileges in order to install files in these locations.

Compilation Requirements

For compiling C/C++ you will need to set the library and include paths per your installation. The include path must include the akalib/include directory and the library path must include either the akalib/{os-arch}/lib or akalib/{os-arch}/lib/static directory. Best practices for how to set these paths are specific to the developer and development environment.

Run-time Requirements

The following discussion covers approaches to using dynamic libraries. None of this is specific to BondOAS™.

Applications linked with a dynamic library will need to be able to find the dynamic library when they are executed. There are a variety of methods for doing this.

Environment Variable

The simplest approach to ensure an application finds a dynamic library is to set the LD_LIBRARY_PATH variable under Unix, the DYLD_LIBRARY_PATH under darwin (Mac OsX), or the PATH variable under Windows. These must include the directory where the dynamic library is installed. The path can be amended in the user's environment through scripts, login files, or other user configuration options. For Windows specific instructions see the discussion of Windows PATH configuration below.

System Configuration

Each operating system provides a mechanism to set the search path for dynamic libraries at a system wide level. You will obviously need to have root or (under Windows) administrative privileges in order to perform these steps.

Sun Solaris

Sun Solaris uses crle to configure how ld.so searches for dynamic libraries. To add a path to the system wide configuration:

$ crle -u -l /usr/local/lib/akalib/sun32/lib

In the above example, substitute /usr/local/lib/akalib/sun32/lib with your installation location and appropriate architecture (32 or 64 bit)

Linux

Linux uses ldconfig to configure how ld.so searches for dynamic libraries. To add a path to the system wide configuration create a file in /etc/ld.so.conf.d directory which points to the installed library location. For example:

$ echo /usr/local/lib/akalib/linux64/lib > /etc/ld.so.conf.d/bondoas.conf

In the above example, substitute /usr/local/lib/akalib/linux64/lib with your installation location and appropriate architecture (32 or 64 bit)

Now update the ld cache.

$ ldconfig

Windows

Windows uses the PATH variable for both executables and dlls. Modifying the PATH variable permanently for either a user or on a system wide basis is done through the System Properties Dialog window. The following discussion for Java installations is instructive: http://java.com/en/download/help/path.xml

Contents