dvipng: Configure
2.2 Configure
=============
The first step is to configure the source code, telling it where various
files will be. To do so, run
./configure OPTIONS
(Note: if you have fetched dvipng from CVS rather than a regular
release, you will have to first generate './configure' by running
'autoconf' 2.53 or later.)
On many machines, you will not need to specify any options, but if
'configure' cannot determine something on its own, you'll need to help
it out. For a list of the options type
./configure --help
On some machines, the libraries will be installed in directories that
are not in the linker's search path. This will generate an error when
running './configure', indicating that it cannot find libgd or
libkpathsea (most likely). You then need to specify the path to the
respective library's object files. They are typically called e.g.,
'libgd.a' or 'libgd.so'. If they are located in e.g., '/sw/local/lib',
do
./configure LDFLAGS=-L/sw/local/lib
If the library is available as a shared object file ('.so'), the
runtime linker may also need to be told where to find the library, then
use
./configure LDFLAGS='-L/sw/local/lib -R/sw/local/lib'
When either of these is necessary, it is likely that the C header
files are also installed in directories that are not in the C
preprocessor's search path. This will also generate an error when
running './configure', indicating that it cannot find e.g., 'gd.h' or
'kpathsea.h' (most likely). You then need to specify the path to the
respective library's C header files. If they are located in e.g.,
'/sw/local/include', do
./configure CPPFLAGS=-I/sw/local/include
On my SUN Solaris workstation, I had to combine this into
./configure CPPFLAGS='-I/sw/local/include -I/sw/tex/teTeX/1.0/include'\
LDFLAGS='-L/sw/local/lib -R/sw/local/lib -L/sw/tex/teTeX/1.0/lib/'
where the backslash denotes a continuation of the line.
Info Catalog
dvipng: Prerequisites
dvipng: Installation
dvipng: Build/install