After checking that you have the
necessary prerequisites,
unpack the tarball, then run ./configure
, and
then make
, make install
,
as usual.
If you intend to use only the pure XSLT version of docbook2X,
then you do not need to compile or build the package at all.
Simply unpack the tarball, and point your XSLT processor
to the XSLT stylesheets under the xslt/
subdirectory.
(The last make install
step, to install
the files of the package onto the filesystem, is optional. You may use
docbook2X from its own directory after building it, although in that case,
when invoking docbook2X, you will have to specify some paths manually
on the command-line.)
You may also want to run make check
to do some
checks that the package is working properly. Typing
make -W docbook2X.xml man texi
in
the doc/
directory will rebuild
docbook2X’s own documentation, and can serve as an additional check.
You need GNU make to build docbook2X properly.
If you are using the CVS version, you will also need the autoconf and automake
tools, and must run ./autogen.sh
first. But
see also the note below about the CVS version.
If you want to (re-)build HTML documentation (after having installed Norman Walsh’s DocBook XSL stylesheets), pass --with-html-xsl
to ./configure
. You do not really need this,
since docbook2X releases already contain pre-built HTML documentation.
Some other packages also call their conversion programs
docbook2man and docbook2texi;
you can use the --program-transform-name
parameter to
./configure
if you do not want docbook2X to clobber
over your existing docbook2man or
docbook2texi.
If you are using a Java-based XSLT processor,
you need to use pass --with-xslt-processor=saxon
for
SAXON, or --with-xslt-processor=xalan-j
for
Xalan-Java. (The default is for libxslt.)
In addition, since the automatic check for the installed JARs is not
very intelligent, you will probably need to pass some options
to ./configure
to tell it where the JARs are.
See ./configure --help
for details.
The docbook2X package supports VPATH builds (building in a location other than the source directory), but any newly generated documentation will not end up in the right place for installation and redistribution. Cross compilation is not supported at all.
For other docbook2X problems, please also look at its main documentation.