Build individual \s-1gnu\s0 shtool scripts
\s-1GNU\s0 shtool \s-12.0.8 (18-Jul-2008)\s0
shtoolize [-h] [-v] [-q] [-o script] module [ module ... ]
The shtoolize program builds individual \s-1GNU\s0 shtool scripts (written to the default output file \*(C`shtool\*(C' or to the specified script) out of one or more shtool ingredient modules. Available modules are:
echo Print string with optional construct expansion mdate Pretty-print modification time of a file or dir table Pretty print a field-separated list as a table prop Display progress with a running propeller move Move files with simultan substitution install Install a program, script or datafile mkdir Make one or more directories mkln Make link with calculation of relative paths mkshadow Make a shadow tree fixperm Fix file permissions inside a source tree rotate Rotate a logfile tarball Roll distribution tarballs subst Apply sed(1) substitution operations platform Platform identification utility arx Extended archive command slo Separate linker options by library class scpp Sharing C Pre-Processor version Generate and maintain a version information file path Deal with program paths
Additionally there is a pseudo-module ``\*(C`all\*(C''' which can be used as a short-hand for ``\*(C`echo mdate table prop move install mkdir mkln mkshadow fixperm platform arx slo scpp version path\*(C''', i.e. to build a shtool script with all modules in the standard order. An installed shtool is usually built this way via ``\*(C`shtoolize -o shtool all\*(C'''.
Use the shtoolize program to build individual shtool scripts in case you want a smaller sized script and you don't need all of the available shtool functionality. For instance for the classical Autoconf based free software package a \*(C`shtool\*(C' script build via ``\*(C`shtoolize -o shtool install mkdir\*(C''' might be sufficient.
The following command line options exist:
Displays a short help page describing the usage of shtoolize.
Displays the version number of shtoolize/shtool.
Displays no processing information.
Writes the output to file script instead to file ``\*(C`shtool\*(C'''.
The typical free software package which is based on \s-1GNU\s0 libtool and \s-1GNU\s0 shtool one uses a \*(C`Makefile\*(C' entry like the following:
# Makefile entry for upgrading GNU tools upgrade-tools: libtoolize -f -c shtoolize -q all
This upgrades the three files \*(C`ltmain.sh\*(C', \*(C`ltconfig\*(C' and \*(C`shtool\*(C' in the current source tree to the latest versions.
shtool\|(1).
Ralf S. Engelschall [email protected] www.engelschall.com