Edit
kc3-lang/automake/TODO
Tom Tromey
- TODO
-
* in --cygnus, clean-info not generated at top level * what if an element of a scanned variable looks like $(FOO).$(BAR) ? or some other arbitrary thing? right now we try to cope, but not very well * update text in missing avoid passive voice * if `interlock' exists, that should be an error (?) should also warn about using new ylwrap and not old one only do this when looking for ylwrap ** make sure every variable that is used is also defined * make sure `missing' defines are generated * if no AM_INIT_AUTOMAKE, then don't handle `missing' stuff. Yuck! * missing should handle install -d and rmdir -p (for uninstall) * allow 'cygnus' in AUTOMAKE_OPTIONS * a couple ways to be smarter: - notice when a .c file is a target somewhere, and auto-add it to BUILT_SOURCES - notice a target of the form `.x.y:' and assume it is a suffix rule * NORMAL_INSTALL / NORMAL_UNINSTALL -vs- recursive rules [ requires changes to the standard ] * if foo.y is a source, foo.h isn't auto-distributed? * dependency tracking doesn't work well when a file is removed the new code to track header dependencies exacerbates this what is the fix? it would probably be better to use "gcc -MD" and move the .d file into the .deps directory. That is, create the dependencies as a side effect of compilation This still won't solve the file-deletion problem [ also: jim makes distributions by checking out, configuring, and running "make dist". This scheme would cause that to fail ] * copyrights on m4 files, aclocal output * is there a way to add a directory and then have "make" do all the updating? think. * put standards.texi into distribution * should not put texiname_TEXINFOS into distribution should rename this macro anyway, to foo_texi_DEPENDENCIES * *all* installed scripts should support --version, --help * have aclocal diagnose unrecognized AM_ macros For now I guess I'll just have automake give an error if it encounters non-C source in a libtool library specification. * must split $obj into two parts: one for libtool and one for deansification. Otherwise .S files will be deansified! * if program has the same name as a target, do something sensible: - if the target is internal, rename it - if the target is mandated (eg, "info"), tell the user consider auto-modifying the program name to work around this * should separate actual options from strictness levels strictness should only cover requirements You should be able to pick and choose options should clean up texinfos.am; one rule is repeated 3 times, but shouldn't be should always use perl -w rewrite in guile (RMS request) at the same time, consider adding a GUI could use the same parsing code for the GUI and the standalone version that means figuring out a better representation of internal state [ that's easy -- anything is better than what we have now ] having just one Makefile for a project would give a big speed increase for a project with many directories, eg glibc. ideally (?) you'd still be able to have a Makefile.am in each directory somehow; this might make editing conceptually easier. * finish up TAGS work * `acinstall' * put parser.h into distribution if "yacc -d" is used * 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 Further: - man page fixes Avoid loops when installing; instead unroll them in automake * 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 ] * for multi-":" mode and AC_OUTPUT, it might be good to pick the first input file that has a corresponding .am file. 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. * Handle `include' lines by scanning other files, and adding to Makefile.in dependency 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. !! 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? Jim's idea: should look for @setfilename and warn if filenames too long * guess split size ** 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