CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
We provide Debian GNU/Linux and Redhat packages for YAZ. Only i386 binary packages are available. You should be able to create packages for other CPU's by building them from the source package.
Note that if your system doesn't have a native ANSI C compiler, you may have to acquire one separately. We recommend GCC.
If you wish to use character set conversion facilities in YAZ or if you are compiling YAZ for use with Zebra it is a good idea to ensure that the iconv library is installed. Most Unixes today already have it - if not, we suggest GNU iconv.
Generally it should be sufficient to run configure without options, like this:
The configure script attempts to use use the C compiler specified by the CC environment variable. If not set, GNU C will be used if it is available. The CFLAGS environment variable holds options to be passed to the C compiler. If you're using Bourne-compatible shell you may pass something like this to use a particular C compiler with optimization enabled:
To customize YAZ, the configure script also accepts a set of options. The most important are:
When configured, build the software by typing:
The following files are generated by the make process:
If you wish to install YAZ in system directories /usr/local/bin, /usr/local/lib .. etc, you can type:
You probably need to have root access in order to perform this. You must specify the --prefix option for configure if you wish to install YAZ in other directories than the default /usr/local/.
If you wish to perform an un-installation of YAZ, use:
This will only work if you haven't reconfigured YAZ (and therefore changed installation prefix). Note that uninstall will not remove directories created by make install, e.g. /usr/local/include/yaz.
This section describes how to compile - and link your own applications using the YAZ toolkit. If you're used to Makefiles this shouldn't be hard. As for other libraries you have used before, you have to set a proper include path for your C/C++ compiler and specify the location of YAZ libraries. You can do it by hand, but generally we suggest you use the yaz-config that is generated by configure. This is especially important if you're using the threaded version of YAZ which require you to pass more options to your linker/compiler.
The yaz-config script accepts command line options that makes the yaz-config script print options that you should use in your make process. The most important ones are: --cflags, --libs which prints C compiler flags, and linker flags respectively.
A small and complete Makefile for a C application consisting of one source file, myprog.c, may look like this:
The CFLAGS variable consists of a C compiler directive that will set the include path to the parent directory of yaz. That is, if YAZ header files were installed in /usr/local/include/yaz, then include path is set to /usr/local/include. Therefore, in your applications you should use
For Libtool users, the yaz-config script provides a different variant of option --libs, called --lalibs that returns the name of the Libtool acrhive(s) for YAZ rather than the ordinary ones.
For applications using the threaded version of YAZ, specify threads after the other options. When threads is given, more flags and linker flags will be printed by yaz-config. If our previous example was using threads, you'd have to modify the lines that set CFLAGS and LIBS as follows: