README.GIT 2.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. If you are building from GIT, run the script
  2. ./autogen.sh
  3. first, to make sure that you have all the necessary maintainer tools
  4. are installed and to build the actual configuration files. If you
  5. have just checked out from GIT, you should add the option "--force" to
  6. autogen.sh so that meta data is noticed by autom4te.cache. Then run
  7. ./configure --enable-maintainer-mode
  8. followed by the usual make.
  9. If autogen.sh complains about insufficient versions of the required
  10. tools, or the tools are not installed, you may use environment
  11. variables to override the default tool names:
  12. AUTOMAKE_SUFFIX is used as a suffix for all tools from the automake
  13. package. For example
  14. AUTOMAKE_SUFFIX="-1.14" ./autogen.sh
  15. uses "automake-1.14" and "aclocal-1.14.
  16. AUTOMAKE_PREFIX is used as a prefix for all tools from the automake
  17. page and may be combined with AUTOMAKE_SUFFIX. e.g.:
  18. AUTOMAKE_PREFIX=/usr/foo/bin ./autogen.sh
  19. uses "automake" and "aclocal" in the /usr/foo/bin
  20. directory.
  21. AUTOCONF_SUFFIX is used as a suffix for all tools from the automake
  22. package
  23. AUTOCONF_PREFIX is used as a prefix for all tools from the automake
  24. package
  25. GETTEXT_SUFFIX is used as a suffix for all tools from the gettext
  26. package
  27. GETTEXT_PREFIX is used as a prefix for all tools from the gettext
  28. package
  29. It is also possible to use the variable name AUTOMAKE, AUTOCONF,
  30. ACLOCAL, AUTOHEADER, GETTEXT and MSGMERGE to directly specify the name
  31. of the programs to run. It is however better to use the suffix and
  32. prefix forms as described above because that does not require
  33. knowledge about the actual tools used by autogen.sh.
  34. Please don't use autopoint, libtoolize or autoreconf unless you are
  35. the current maintainer and want to update the standard configuration
  36. files. All those files should be in GIT and only updated manually
  37. if the maintainer decides that newer versions are required. The
  38. maintainer should also make sure that the required version of automake
  39. et al. are properly indicated at the top of configure.ac and take care
  40. to copy the files and not merely use symlinks.