Knowledge for our questions, fun for everyone!
Knowledge for our questions, fun for everyone!

Setting up libtool

Overview
Setting up libtool
Overview

Index

  1. Introduction
  2. Arch & compiler overview
  3. Requirements
  4. Uncompress distro
  5. Choose install directory
  6. Configuring Makefile
  7. Compiling and installing
  8. Using the library
  9. Bugs & support

Introduction

This library provides some generic, useful tools to manage time, errors, locks, and so on. This library is part of a bigger project called IT/m, but you can use it as standalone library. In this section are covered the installation and configuration steps.

Arch & compiler overview

This library has been developed using a g++ 2.95.2 version. Also, It has been tested in a 2.95.3 version, and it works. My libc library version is 2.1.3. The distribution is a Debian potato 2.2. Finally, my arch is a intel 686 processor, with a 2.2.17 kernel.

Requirements

You need at least, the 2.95.2 g++ compiler a gnu makefile and the linux threads installed. If you plan to mess up with the pgadapter class, you need also a working postgressql environment, with all the include and library files propertly installed. For install and setup this RDBMS, see the postgresql web site. The version of postgresQL used for test and developement is 7.1.1

The developement platform is a linux (intel) box, so if you plan to migrate this library to other platform, please send me the patches to include them in the main developement tree.

Uncompress distro

The first thing is uncompress the distribution in a directory. For example, I will use the /tmp directory:

	halt% tar xfz libtool-0_85.tar.gz 
	halt% cd libtool_0_85
        halt% pwd
        /tmp/libtool_0_85
        halt%

Ok, remember this directory, because we need it in the following step.

Choose install directory

We have to plan where to install the library. For developement pourpouses, is better having this libraries separated from the ’production’ ones, so I usually create a directory in my home, called ’devel’. The only drawback of this configuration, is that you need to setup the LD_LIBRARY_PATH environment variable propertly to handle this directory. If you don’t want to set this variable, you can insert the directory in the /etc/ld.so.conf file and issue a ’ldconfig’ command.

In this example, I choose as install directory /home/assman/devel. So I create it first:

	halt% mkdir -p /home/assman/devel/{include,lib}

Configuring Makefile

Now we go to the libtool directory and edit the Makefile file. In the example, the libtool directory is /tmp/libtool_0_85 so:

	halt% cd /tmp/libtool_0_85
	halt% vi Makefile

First, we find the first variable in the file, BASEDIR and set up to the libtool directory:

	export BASEDIR=/tmp/libtool_0_85

Second, we find the second variable, INSTALLDIR, and set up to the installation directory:

	INSTALLDIR=/home/assman/devel

Now, if you want to add the pgadapter to the library, you have to install the postgresql’s developement enviroment and uncomment the OPTIONAL_ELEMENTS entry in the makefile. For proper work, this makefile assumes that the include files are installed in a place that the compiler can found them (/usr/include) If not, you have to insert the include directories in the INCLUDE variable of the Makefile.

Compiling and installing

Now issue a ’make’ command to compile all the elements of the library, and to build it. If no problem is found, you can install the library in the choosed directory. Note that you need to have write permissions in this directory, so you should become root if you want to install it in a system directory (e.g. /usr/local). Now, issue a ’make install’. This will copy and create all the links and required files.

Using the library

If you plan to use the library for developement, you need to include the header files in your programs, and link with the library to proper work Also, you need to setup the LD_LIBRARY_PATH if you want to run the programs you compile. In our example, a setup for the LD_LIBRARY_PATH can be:

halt% export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/assman/devel

Bugs & support

This library has been in-deep tested, but some bugs can arised. Also, you can have some ideas, or improvements for this library. Please send me an email if you found some bug, if you need support installing this library, of if you port this library to a different platform. Thanks for your help.

Published at 01/01/2004 15:40:50
Last Updated 01/01/2004 17:22:30
By Juan M. Casillas




Google



Setting up libtool
Overview

Sections
LibTool

February's articles
S M T W T F S
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
      
More articles

Search


Other versions
XML version
Printable version

Download
Latest version is 0.86
(27 Kb, tar.gz file)

 » from JMCResearch
Quick links
Install HOW-TO
Local CVS Repository
Ask your questions