|Getting Started with Pivotal GemFire Native Client / Running Native Client Applications|
This section describes how to build and run a native client application on Solaris.
Set the native client environment variables on each Solaris host. For each case, productDir is the path to the native client product directory.
GFCPP= productDir ; export GFCPP PATH=$GFCPP/bin:$PATH;export PATH LD_LIBRARY_PATH=$GFCPP/lib:$LD_LIBRARY_PATH;export LD_LIBRARY_PATH
Version 5.9 of the SUNpro compiler is supported on Solaris. The linker switches vary according to whether you are statically linking to the GemFire library.
|-D_REENTRANT||Required to compile Solaris programs in a thread-safe way.|
|-xarch=v8plus||Enables 32-bit compilation.|
|-xarch=v9||Enables 64-bit compilation.|
|-ldl; -lpthread; -lc; -lm; -lsocket; -lrt; -lnsl; -ldemangle; -lkstat; -lz||Additional libraries.|
|-library=stlport4||Solaris library compilation.|
|-I$ GFCPP /include||Specifies the GemFire include directory.|
When a C++ application is not statically linked to the GemFire library, the library must be dynamically loadable.
To verify that the GemFire library is available for loading, make sure you have added the path GemFireDir/lib to the LD_LIBRARY_PATH environment variable, where GemFireDir is the path to the GemFire product directory.