3.4 Advanced build features

This section documents features that are unlikely to be used but deserve a bit of documentation.

A ./configure switch, ‘--with-unicode’ allows to choose whether the unicode code should be used or not. The default is to detect it with a test. This code requires Encode and Unicode::Normalize modules.

A similar ./configure switch, ‘--with-unidecode’ allows to choose whether the perl module Text::Unidecode should be used or not. The default is to detect it with a test. This code requires the Text::Unidecode module.

perl isn't needed to build the script. the script is build by ‘./configure’ and a shell script launched by make which is a simple wrapper around a sed one-liner. The perl command can be specified with the environment variable $PERL, otherwise it is detected. perl is required to rebuild the documentation as the HTML documentation is rebuild with texi2html itself.

The translations are managed by a script manage_i18n.pl, created by ./configure. manage_i18n.pl requires Data::Dumper to function normally. If this module isn't there ./configure detects it and manage_i18n.pl doesn't really rebuild the translations, but only copy files. It is possible to use the ./configure switch ‘--enable-translations’ to override the ./configure detection. For more about translations, see Internationalization.

It is possible to build from outside of the source directory, for example the following should work:

tar xzvf texi2html-No value for VERSION.tar.gz
mkdir texi2html_build
cd texi2html_build
../texi2html-No value for VERSION/configure && make

All these features enables to build texi2html on a platform in order to run it on another platform, a kind of cross-building. The ./configure switches and $PERL allows to specify everything needed for the build of the texi2html script.

Doku-Base