Configuring GeoStan - geostan_1 - 2024.01

Understanding the symbolic constants of GeoStan

The C header file, geostan.h, contains all symbolic constants used or returned by the GeoStan functions. Precisely recommends you review this file before using any GeoStan functions. geostan.h is the proper include file for all C environments.

For each return value, GeoStan defines the maximum length of the value. Symbolic constants use the naming convention <<NAME>>_LENGTH. For example the enum GS_ADDRLINE returns the input or output address line. The maximum length of an address line is 61. Therefore, the symbolic constant is GS_ADDRLINE_LENGTH and is defined as 61.

Using GeoStan on Windows

When using GeoStan on Windows, be sure to define the _WINDOWS symbol. To successfully use GeoStan on Windows, your project must define one or both of the following: __NT__ and _WIN32. You are not warned with compile or link errors if you fail to define these symbols; however, your application will not function properly, and can result in insufficient stack space. Microsoft compilers typically define these symbols for you, but Precisely strongly recommends that you define them in your project for completeness.

Using GeoStan on UNIX

Although Precisely builds GeoStan using the latest technology available, some UNIX developers may encounter difficulties caused by compiler-specific problems or system dependencies. This section explores some peculiarities of the compiler used in the UNIX environment.

Object dependencies and standard link libraries

Because UNIX kernels typically have few dependencies and do not require all the standard development environment libraries and files, some standard link libraries (such as the C++ class library) are not included with the "cc" system configuration compiler. GeoStan requires certain standard libraries that are available on every UNIX development platform, but which the application may not find unless you install the appropriate system option.

To determine what system libraries are needed, run the "ldd" command (http://linuxmanpages.com/man1/ldd.1.php).

For example ldd libgeostan.so in GeoStan 30.00 returns the following on RH Linux:

linux-vdso.so.1 => (0x00007fff555fe000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f9b1a61a000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f9b1a3fe000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f9b1a0f6000)
libm.so.6 => /lib64/libm.so.6 (0x00007f9b19df4000)libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f9b19bde000)
libc.so.6 => /lib64/libc.so.6 (0x00007f9b1981c000)
/lib64/ld-linux-x86-64.so.2 (0x00007f9b1ad79000)

The standard libraries used by GeoStan are:

• C++ class library, such as libC.so, libC.sl, and libC.a.
• Math library, such as libm.a, libm.so, and libm.sl.
• C library, such as libc.a, libc.so, and libc.sl.

See the sample make files included as part of the installation for the libraries needed for your system.

Installing libraries and shared libraries

The UNIX system can recognize development libraries when placed in the system environment variables library path. On most systems, the path for this variable is /lib:/usr/lib. Some systems may include additional library directories needed for specific applications or configurations. When a library file has a name such as libname.a, libname.so, or libname.sl (HPUX only), the UNIX system recognizes the library by default as long as it is in the library path.

The GeoStan library is distributed with the names libgeostan.so or libgeostan.sl (HPUX only). To guarantee your system can locate the needed GeoStan libraries, you should include the full path to your precisely/geostan directory in your systems library search path. For example:

• AIX: LIBPATH=/usr/precisely/geostan:$LIBPATH ; export LIBPATH
• Solaris and Linux: LD_LIBRARY_PATH=/usr/precisely/geostan:$LD_LIBRARY_PATH ; export LD_LIBRARY_PATH
• HP-UX: SHLIB_PATH=/usr/precisely/geostan:$SHLIB_PATH ; export SHLIB_PATH

Using GeoStan on z/OS