Developer's Guide
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Macros Groups Pages
Deploying SKC

Table of Contents

Overview

Deploying SKC with your application is easy. All the SKC related files must be in the same directory (shared libraries, registry, and language files) as your application binary. Please see SKC Redistributibles for the list of redistributable files.

For example, if your application is installed in /opt/your_app on Linux and is an optimized build, you would need to copy the following SKC files from the linux/Linux2.6_x86_OPT_32bit.OBJ/components and linux/Linux2.6_x86_OPT_32bit.OBJ/lang directories to /opt/your_app directory:

  • runtime.dat
  • libp6loader.so
  • libp6ltcore.so
  • libp6json.so
  • p6json.en_us
  • linux-langtag.txt (See Language Files below)

Language Files

Each SKC platform directory contains a copy of the language string table files in the lang directory. These files are the same on all platforms and are included in each directory for convenience. The language files contain UTF-8 encoded strings that the SKC components use for various things (for example logging).

There is a different "langtag" file for each platform, however, and the correct platform specific langtag file must be deployed on each platform. The langtag files map the operating system specific locale to P6R platform independent locale string. These platform independent locale strings are used as the files extention of the language string tables files for a given locale.

  • Windows: deploy windows-langtag.txt
  • Linux: deploy linux-langtag.txt
  • Solaris: deploy solaris-langtag.txt