* Document why putting @FOO@ in _SOURCES doesn't work.
This must be done for 1.5
-* ylwrap should support flex's -P option
- also it should be integrated into missing, probably
-
* think about how per-object flags should work. in particular:
* how should they be specified?
using the object name is confusing when .lo/.obj in use
unfortunately it isn't that useful until autoconf has support
for this sort of thing as well ]
-* if automake -a, and dangling links exist, automake should
- remove and reinstall
-
-* add a way to require C++ support even when no apparent C++ code
- exists. Likewise for other langs.
- eg, `extension-cxx' option
- (is this really needed?)
-
-* Add a way to say that foo/bar.h should be installed as
- $(includedir)/foo/bar.h without introducing a new dir var
-
* distcheck should make sure that each file that uses _() is
listed in POTFILES.in
From Jim Meyering:
* support prog_LIBS as override for LIBS
-* Sometimes we can warn about a missing `compile' script twice.
-
-* A target named `INSTALL' will screw things up.
- It shouldn't.
-
* Scan configure.in using the same trick that autoheader uses.
This will be much more reliable.
This will be a problem for any macro defined internally
[ fixing this will probably fix the nasty `exeext redefines
foo_PROGRAMS' hack that is in there right now ]
- In some cases this is unfixable. In these cases we should give
- an error. This can be done by keeping track of whether a macro
- was assigned with `=' or `+=', and having define_variable give
- an error if the variable exists and was defined with +=.
+ [ we currently give an error when this occurs, so this is very low
+ priority ]
* document user namespace for macro/target names
adopt some conventions and use uniformly
[ use user-written suffix rules to generate the per-file rules in
an automatic way -- this would be mucho cool ]
-* Allow for multiple translations of a texinfo file:
- LL_info_TEXINFOS = ...
- will put info files for language LL into $(infodir)/LL.
-
-* If you suppress an internal variable by specifying a variable
- in a Makefile.am, but the variable is conditional, then automake
- should generate the internal variable conditionally.
- You have to scan the map of all conditions and fill in the holes here
-
* Every program foo has FOOFLAGS right now.
It should also have AM_FOOFLAGS, which can be set in Makefile.am.
DONE: but needs to be documented
-* Should be able to update files that would be installed with -a
- (--force?)
-
* "make diff" capability
look at gcc's Makefile.in to see what to do
or look at maint program
-* define LINK if a program is mentioned, even if no C sources appear
-
* BUILT_SOURCES should not be distributed, even when they appear in
another _SOURCES line. [? or maybe just leave this up to the
to-be-defined generic distribution method ]
right now we try to cope, but not very well
[ this is only of theoretical interest for now ]
-** make sure every variable that is used is also defined
+* make sure every variable that is used is also defined
[ we don't really look at variable uses in detail.
2.0 thing ]
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?
-
* copyrights on m4 files, aclocal output
-* is there a way to add a directory and then have "make" do all the
- updating? think.
-
* should not put texiname_TEXINFOS into distribution
should rename this macro anyway, to foo_texi_DEPENDENCIES
* finish up TAGS work
* `acinstall'
-* put parser.h into distribution if "yacc -d" is used
* only remove libtool at top level?
!! 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? [ I think you can ]
-
Jim's idea: should look for @setfilename and warn if filenames too long
* guess split size
configure.in). Then built man pages (eg) could automatically be
omitted from the distribution.
-Idea from Joerg-Martin Schwarz: allow passing different -D flags to
-different compiles. This can be done, but with the restriction that a
-.c cannot appear in 2 different "objects" (programs/libraries)
-compiled with different -D options (because -c and -o do not always
-work together and parallel makes must work). This could be
-implemented by noticing whenever a ".o" target with no rules is being
-emitted, and adding the appropriate compilation rule as appropriate.
-This should work with targets from Makefile.am as well as from .P
-files, which means rewriting so that the Makefile.am contents aren't
-copied into the output immediately.
- [ this could be probably done more directly by examining the sources
- as we scan Makefile.am ]
-
Henrik Frystyk Nielsen says:
Henrik> 4) Flags like --include-deps are lost when you make changes to
Henrik> Makefile.am files and automake is run automatically. It would
git://sourceware.org / automake.git / commitdiff