next up previous contents index
Next: Notes on Using GNU Up: Getting Started Previous: Getting Started   Contents   Index


Building, Installing and Removing the t1lib-Package

As of version 0.2-beta, the autoconf-package is used to configure and build the library. imake is no longer supported. Furthermore, starting with version 0.8-beta GNU libtool is used for managing library-specific stuff.

Here is how to build and install t1lib:

  1. Change to T1-directory.
  2. Run ./configure. This will check your system's setup and generate the Makefiles. By default, shared and static versions of the libraries are built.

    Specifying --disable-shared or --disable-static as a commandline option to configure will suppress the generation of the respective library type. Of course, these rules are superseded by the capability of the system to manage those library types.

    If you know shared libraries are supported on your system but configure says that no dll can be built, some compiler option may be setup incorrect. Please refer to ([*]).

    If the X11 window system is installed on the target system t1lib is automatically build with special X11 support. In cases where this is explicitly not desired the commandline option --without-x may be used to configure a library without extended X11 support. In this case the test program xglyph is also not build since it needs X11.

  3. Run make. This will build all the stuff including the documentation. If you do not have LATEX2e run make without_doc. This will skip generating the documentation.
  4. Type make install to install the package. You'll probably need to be superuser for installing the package at the standard locations. However, the files may be located wherever the user wants, as long as the compiler finds them at compile time. So, place them where you want.

    The following files are installed when doing a make install:

The top level Makefile further supports the targets clean and distclean. The latter is an extension of clean which also removes the makefiles as well as the log and cache files of the configuration process. It forces thus a new call to configure.

A make clean is needed, for example, if someone experiments with static and shared libraries since the object files for shared libraries require the additional position independent code options.

The directory T1/parse_afm is not needed at all, it is included only for completeness. The parts needed from this have been copied to the lib/t1lib-subdirectory.


next up previous contents index
Next: Notes on Using GNU Up: Getting Started Previous: Getting Started   Contents   Index
2004-10-04