Closed stefanbeller closed 11 years ago
I am not sure about what is the best solution for this problem.
As I see it, there are three options: [1] update the README I don't like this, because it can be misleading to people using the tarball version. [2] include autogenerated files in the repository I don't like this either because of redundancy. But I know that this is the method used by the glibc project, for example. [3] do nothing This is my favourite. I think that people who choose to use the source tree version of an application can be expected to have enough knowledge of autotools and friends to know how to generate a configure file.
I don't have enough knowledge about the autotools, as I never came accross a package, where either the redundant files were missing or were not documented (such as type these 3 commands and you're happy).
I started reading at https://en.wikipedia.org/wiki/Autoconf and assume I'd only need to run autoconf to generate the ./configure script? However:
sb@sb:~/OSS/graprof$ autoconf
configure.ac:13: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:16: error: possibly undefined macro: AM_PROG_CC_C_O
configure.ac:17: error: possibly undefined macro: AM_PROG_AR
configure.ac:18: error: possibly undefined macro: AM_PROG_LEX
configure.ac:31: error: possibly undefined macro: AM_CONDITIONAL
sb@sb:~/OSS/graprof$ autoconf --version
autoconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by David J. MacKenzie and Akim Demaille.
to regenerate all required configure files from the input skeletons (configure.ac, Makefile.am) you have to run
autoreconf --install
I decided to include an autogen.sh file in the source tree, that generates the configure script. I also mentioned this in the README. I hope this will suffice :)
So I was trying out the git version instead of the tarball and there is no ./configure file. Did the install process change?