autoconf - Distributing autotool metafiles -


am_maintainer_mode has been criticized, , believe main objection leads incorrect builds if dependencies on meta-files not detected. also, argued generated files not belong in version control systems (i agree position). believe if configure not belong in vcs, configure.ac , makefile.am not belong in tarball. end, i've written simple script clean targets out of makefile.in , added following target top-level makefile.am:

dist-hook:     @rm $(distdir)/configure.ac     @rm $(distdir)/aclocal.m4     @find $(distdir) -name makefile.am -exec rm {} \;     @find $(distdir) -name makefile.in -exec $(top_srcdir)/clean-makefile {} \; 

this solution sidesteps problematic issues derive am_maintainer_mode because there no meta-files modified.

it strikes me 1 of biggest failings of autoconf misperception every project built using has dependency on autoconf (this not autoconf failing, failing of marketing/education), , misperception largely result of tarballs containing meta-files.

question: there better way accomplish desired goal of creating tarball not contain autotool metafiles? (the question of whether goal merely 'arguably undesirable' or 'truly evil' open forum!)

there may way this, automake wouldn't support if there was.

automake's primary goal implement gnu coding standards regarding makefiles. and, tenet of gnu users should given primary sources hack on -- requirement of gpl.

shipping derived files not sources against idea.

i think theory here misguided. users benefit having source. example, it's reasonably common have hack configury or build scripts; , simpler source code.


Comments

Popular posts from this blog

c# - SVN Error : "svnadmin: E205000: Too many arguments" -

c++ - Using OpenSSL in a multi-threaded application -

All overlapping substrings matching a java regex -