1 files changed, 784 insertions, 23 deletions

diff --git a/bootstrap b/bootstrap
index 7589553..5a3ce01 100755
--- a/bootstrap
+++ b/bootstrap
@@ -1,23 +1,784 @@
-#! /bin/sh
-
-chksrc() {
-    test -f modinc || return 1
-    test -f stub.ac || return 1
-    src=`sed -n 's/AC_CONFIG_SRCDIR(\[\(.*\)\]).*/\1/p' stub.ac`
-    test -n "$src" || return 1
-    test -f $src
-}
-
-if ! chksrc; then
-    echo "$0: must be run from the Dico source tree root directory"
-    exit 1
-fi
-
-set -e
-git submodule init
-git submodule update
-./modinc
-set +e
-gnulib=gnulibinit
-test -L $gnulib || ln -sf ./gnulib/build-aux/bootstrap $gnulib
-./$gnulib
+#! /usr/bin/perl
+# This file is part of GNU Dico
+# Copyright (C) 2014, 2016 Sergey Poznyakoff
+#
+# GNU Dico is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3, or (at your option)
+# any later version.
+#
+# GNU Dico is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with GNU Dico.  If not, see <http://www.gnu.org/licenses/>.
+
+=head1 NAME
+
+bootstrap - Bootstrap the Dico project
+    
+=head1 SYNOPSIS
+
+B<bootstrap>
+[B<-ahmnv>]    
+[B<--add>]
+[B<--help>]    
+[B<--new>]
+[B<--modules>]    
+[B<--dry-run>]
+[B<--verbose>]
+[I<NAME>...]
+
+=head1 DESCRIPTION
+
+Bootstrap the Dico project.  This is the first command that should be run
+after cloning the project from the repository in order to be able to built
+it.
+
+When run without arguments performs the following actions:
+
+=over 4
+
+=item 1. Pulls in git submodules.
+
+=item 2. Creates autoconf/automake sources for building Dico modules.
+
+Recreates F<configure.ac> and F<modules/Makefile.am> from stub files
+F<configure.boot> and F<modules/stub.am>.  The list of modules is obtained
+from the contents of the F<modules> directory -- each subdirectory
+is supposed to contain one module.
+
+Additional F<configure.ac> code for each module is obtained from
+file F<module.ac> in each module directory.  See the description of
+this file in section B<FILES>.
+
+=item 3. Bootstraps the B<gnulib> submodule.
+
+=back    
+
+The program must be run from the Dico source tree topmost directory.
+    
+When given the B<-m> (B<--modules>) option, only the second step is
+performed.
+
+When run with B<-a> (B<--add>, B<--new>) option, the program creates
+basic infrastructure for modules named in the command line.  For each
+I<NAME> it creates directory F<modules/I<NAME>>.  Withih that directory,
+it creates two files: F<Makefile.am> from F<modules/template.am>, and
+F<I<NAME>.c>, which contains a stub code for the module.  The new module
+is then integrated into F<configure.ac> and F<modules/Makefile.am> files.    
+
+By default, the program prints only error diagnostics.  That means that
+upon success, it will terminate quietly, without producing a single line
+on output.  This can be changed using the B<-v> (or B<--verbose>) option.
+When the option is given once, the program prints general description before
+running each of the three steps described above.  Two B<-v> options instruct
+it to also print whatever output that was generated when running auxiliary
+commands.  Finally, three B<-v>'s produce additional debugging information.    
+
+The B<-n> (B<--dry-run>) option instructs the tool to print what would have
+been done without actually doing it.
+    
+=head1 OPTIONS
+
+=over 4
+
+=item B<-a>, B<--add>, B<--new>
+
+Create basic infrastructure for modules named in the command line and
+add them to F<configure.ac> and F<modules/Makefile.am>
+    
+=item B<-n>, B<--dry-run>
+
+Don't do anything, just print what would have been done.    
+
+=item B<-m>, B<--modules>
+
+Run only the second step: creation of autoconf/automake sources for
+Dico modules.     
+    
+=item B<-v>, B<--verbose>
+
+Increase output verbosity.  Multiple options accumulate.    
+
+=back
+
+The following options are passed to the B<gnulib> bootstrap script
+verbatim:
+
+=over 4
+
+=item B<--gnulib-srcdir=>I<DIRNAME>
+    
+Specifies the local directory where B<gnulib> sources reside.  Use this if
+you already have gnulib sources on your machine, and do not want to waste
+your bandwidth downloading them again.
+
+=item B<--no-git>
+
+Do not use git to update B<gnulib>.  Requires that B<--gnulib-srcdir> point
+to a correct gnulib snapshot.
+
+=item B<--skip-po>
+
+Do not download po files.
+    
+=back    
+    
+The following options cause the program to display informative text and
+exit:    
+    
+=over 4    
+    
+=item B<-h>
+
+Show a short usage summary.
+
+=item B<--help>
+
+Show man page.    
+
+=item B<--usage>
+
+Show a concise command line syntax reminder.     
+    
+=back
+    
+=head1 FILES    
+
+The following files are used as templates to create output files.  When
+creating output file, each line from the corresponding template is read,
+I<macro expansion> is performed, and the resulting string is written to the
+output file.
+
+During macro expansion, each occurrence of B<< <I<NAME>> >> is replaced with
+the contents of the macro variable I<NAME>, if it is defined.  Expansion
+of undefined variables leaves the text as is.
+
+The construct B<< <I<NAME>#I<TEXT>> >> is expanded if it appears on a line
+alone, possibly preceded by any string of characters.  It works similarly
+to B<< <I<NAME>> >>, except that if I<NAME> expands to multiple lines, the
+second and subsequent lines of expansion are prefixed with I<TEXT> on output.
+If I<TEXT> is empty, the content of the source line immediately preceding the
+construct is used instead.  This makes it possible to use expansions after a
+comment character.  E.g. if the variable B<HEADING> contains:
+
+    This file is generated automatically.
+    Please, do not edit.
+    See the docs for more info.
+
+and the input file contains:
+
+    dnl <HEADING#>
+
+Then, the resulting expansion will be:    
+
+    dnl This file is generated automatically.
+    dnl Please, do not edit.
+    dnl See the docs for more info.
+
+The macro variables are specific for each file, and are described below.
+
+For each file, a special comment sequence is defined.  Lines beginning
+with that sequence are omitted from the output.    
+    
+=over 4
+
+=item F<configure.boot>
+
+Produces the F<configure.ac> file.  Comment marker is B<##>.
+The following variables are defined:
+
+=over 8
+
+=item B<MODULES>
+
+B<Autoconf> code for each module, obtained from the F<module.ac>
+files.
+
+=item B<HEADING>
+
+Generates an initial header text, warning the reader that the file is
+generated automatically and informing him about the ways to recreate
+that file.
+
+=item B<STATUS_OUTPUT>
+
+A list of printable description for modules that can be disabled.  Each
+module is represented with a line
+
+    MODNAME ................ STATUS
+
+where MODNAME is the module name and STATUS is the module status variable
+(which produces B<yes> or B<no> at configure time, depending on whether
+the module is enabled or not).
+
+This is intended for use in B<AC_CONFIG_COMMANDS>.    
+
+=item B<STATUS_DEFN>    
+
+A list of assignments for module status variables, intended
+for use in B<AC_CONFIG_COMMANDS>.
+
+=back
+
+The following code illustrates the use of the latter two variables:
+
+  AC_CONFIG_COMMANDS([status],[
+echo<STATUS_OUTPUT>                    
+],
+                     [<STATUS_DEFN>])
+    
+=item F<modules/*/module.ac>
+
+This file is optional.  If present, it contains the B<autoconf> code for