Blithe SDK


Blithe provides a shared library and a static library to allow you to retrieve entries and other information from the dictionaries. Why two libraries? The shared library contains the real functionality, such as getting the appropriate string for a given language. The static library provides glue in case the shared library is not present. If the shared library is not present, the static library will look at entries contained inside your application and ignores the language ID arguement.

Shared Library

Blithe.so is the Blithe shared library. To use it, put it in /boot/home/config/lib. You may add it to your project, but this is discouraged because your application will crash if blithe.so is not in /boot/home/config/lib. Blithe.so only exports C functions.

Static Library

Blithestatic.o is a static library. There are C functions and a C++ wrapper class. The C functions are named the same in blithestatic.o and blithe.so. Blithestatic.o allows your application to run without blithe.so, but it will call through to the shared library if it is present. If you use blithestatic.o, you should create a special dictionary (the language can be of your choosing) which consists of all of the strings that you use including common dictionary strings. You should add this file to your project. The static library adds appoximately 6K to your application.

Headers

Header Include this if using...
Blithe.h The static library with the C API.
BlitheDictionary.h The static library with the BlitheDictionary class.
BlitheLib.h The shared library. Using the shared library directly is discouraged, since the static library provides weak linking with the shared library.
BlitheConst.h Any part of Blithe. Provides constants including messages, language IDs, and entry IDs for the common dictionaries.

Source

Source code for the static and shared libraries is included for debugging purposes. Please do not distrubute modified source without permission.