Edit
kc3-lang/automake/TODO
Tom Tromey
- TODO
-
Priorities for release: !! documentation (eg new macros) !! finish up TAGS work * `acinstall' * echo in installs? * `missing' program * copyrights on m4 files, aclocal output * for new autoconf: * completely handle multi-":" mode for AC_CONFIG_HEADER * Scan multiple input files when Makefile is generated? This would provide flexibility for large projects; subsumes the "Makefile.tmpl" idea [ can't do this. must explain why in manual. basically, solving all the problems is too hard like: how to remove redundancies between generated .in files instead should implement `include' directive for Makefile.am ] * figure out what to pass as CONFIG_HEADER to config.status * look @ jim's $(t:=foo) problem * should install-foo target for a new dir (eg fooexecdir) be run via install-data or install-exec? Consider examining name of variable. * no mention of $(LIBTOOL) in "clean" Makefile (?) * compatibility with older versions of autoconf if not --gnu ================================================================ * only remove libtool at top level? * clean up source directory by moving stuff into subdirs * consider adding pkglibexecdir, maybe others? requests for pkg-dirs with version included Fix ansi2knr so that knr-style function decls aren't incorrectly rewritten. Or, fix automake so that not all sources in a directory must be ansi. Should also fix things so that a separate ._o file is not needed; instead use a wrapper script. Gord on pretty-printing instead of raw loops: Gord> I think the best thing to do is to have make output be a valid shell Gord> script, and to have it be clear exactly what is happening at a given Gord> time. Further: - man page fixes - consider adding "echo"s to installs again. users can use make SHELL='sh -x' to get the full dirt Avoid loops when installing; instead unroll them in automake Some long-term projects: * if $(FOO) is used somewhere, ensure FOO is defined, either by user or by automake if possible * Don't rearrange order of `include' lines relative to += assignments. * Handle += assignments at all. consider putting all check-* targets onto @check? To support --help/--version checking? take diff-n-query code from libit Per Bothner says: Per> 1) Being able to build a set of non-source programs Per> from source programs, without necessarily linking them together. Per> I.e. one should be able to say something like: Per> dummy_SOURCES=foo.c bar.c Per> and automake should realize that it needs to build foo.o and bar.o. Per> 2) Being intelligent about new kinds of suffixes. Per> If it sees: Per> SUFFIXES = .class .java Per> and a suffix rule of the form: Per> .java.class: Per> then it should be able to realize it can build .class files from Per> .java files, and thus be able to generate a list of Per> .class files from a list of .java source files. From Jason Molenda: * allow a way to use "gzip --best" [ Try GZIP=--best make dist ] * don't assume GNU tar is "tar" (eg in distcheck) * actually use acinstall program !! Must fix require_file stuff. It is really gross, and I don't understand it any more. * error messages should print ``[info blah blah]'' command when a certain part of the standards apply. saw idea in message from Craig Burley. wouldn't it be really cool if compile-mode in Emacs understood this convention, and you could click on such text to go to the appropriate info page? !! should write autoconf-style doc entries for each m4 macro Jim's idea: should look for @setfilename and warn if filenames too long * guess split size * allow ".info" to be missing * must update GNU Hello ** many requests for a way to omit a file from the distribution. Should be done like `!foo' or `~foo' in _SOURCES, etc. Such files should be removed explicitly after the copy step! Doing this requires rewriting macros before generating Makefile.in. from joerg-martin schwarz: -- If Makefile.am contains $(CC), $(COMPILE), $(YLWRAP), .... in an explicitly written rule, you should emit the corresponding Makefile variables automatically. Configuring in the large: * allow hierarchy of dirs to share one aclocal.m4 How? consider printing full file name of Makefile.am or configure.in when giving error. This would help for very large trees with many configure.in scripts From the GNU Standards. These things could be checked, and probably should be if --gnu. * Make sure that the directory into which the distribution unpacks (as well as any subdirectories) are all world-writable (octal mode 777). * Make sure that no file name in the distribution is more than 14 characters long. * Don't include any symbolic links in the distribution itself. (ditto hard links) * Make sure that all the files in the distribution are world-readable. ** also, check --help output and --version output. Idea from Fran