You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure what we should include in the git tree vs. in the dist tar balls regarding autotools files. In theory, the dist tarball should simply be complete enough to execute ./configure && make to build it, so most stuff would be needed (all the way op to configure and Makefile.in). For the Git repo however, it makes sense to have a developer at least refresh it once when working on the code.
Looking at http://i.stack.imgur.com/SlURG.png it seems to make sense to me to cut off at the configure.ac and Makefile.am line and have people use the bootstrap.sh script as-is to generate their aclocal.m4, config.h.in and Makefile.in on the fly. Since a developer should have all tools anyway to build this stuff, it wouldn't be much of a problem.
Anyone here have any input on this?
The text was updated successfully, but these errors were encountered:
I'm not sure what we should include in the git tree vs. in the dist tar balls regarding autotools files. In theory, the dist tarball should simply be complete enough to execute ./configure && make to build it, so most stuff would be needed (all the way op to configure and Makefile.in). For the Git repo however, it makes sense to have a developer at least refresh it once when working on the code.
Looking at http://i.stack.imgur.com/SlURG.png it seems to make sense to me to cut off at the configure.ac and Makefile.am line and have people use the bootstrap.sh script as-is to generate their aclocal.m4, config.h.in and Makefile.in on the fly. Since a developer should have all tools anyway to build this stuff, it wouldn't be much of a problem.
Anyone here have any input on this?
The text was updated successfully, but these errors were encountered: