autogen.sh

   1 #!/bin/sh
   2 #
   3 # Run this to generate the configuration scripts after a fresh
   4 # repository clone/checkout.
   5 #
   6 # This script does *not* call configure (as usually done in other
   7 # projects) because this would prevent VPATH builds.
   8
   9 step() {
  10     local message="$1"
  11     local command="$2"
  12
  13     printf "$message... "
  14
  15     if eval $command >/dev/null 2>&1; then
  16         printf "\033[32mok\033[0m\n"
  17     else
  18         local result=$?
  19         printf "\033[31mfailed\033[0m\n  ** \"$command\" returned $result\n"
  20         exit $result
  21     fi
  22 }
  23
  24
  25 srcdir=`dirname $0`
  26 test -z "$srcdir" && srcdir=.
  27
  28 step    "Checking for top-level adg directory" \
  29         "test -f '$srcdir/configure.ac' -a -f '$srcdir/src/adg.h.in'"
  30
  31 cd "$srcdir"
  32
  33 step    "Creating dummy ChangeLog, if needed" \
  34         "test -f './ChangeLog' || touch './ChangeLog'"
  35
  36 # Not sure if I can remove these, they seem to be old relics
  37 step    "Calling internationalization scripts" \
  38         "glib-gettextize -f && intltoolize -f"
  39
  40 # autoreconf interaction with libtool has been broken for ages:
  41 # explicitely calling libtoolize seems to avoid some problem
  42 step    "Calling libtoolize" \
  43         "libtoolize --automake"
  44
  45 step    "Regenerating autotools files" \
  46         "autoreconf -isf -Wall"
  47
  48
  49 printf "Now run \033[1m./configure\033[0m to customize your building\n"