4 * clean targets not very well tested
6 Should 'distclean' remove $(SCRIPTS)?
7 Should 'maintainer-clean' do "rm -rf .deps"?
8 Should look for clean-local targets in Makefile.am.
10 Should redo how 'all' target is handled.
12 Consider a --install-missing option to install missing files such as
13 mdate-sh, texinfo.tex, etc.
15 Think about writing a small tool to guess what the local Makefile.am
18 Prettyprint macro definitions, eg:
19 DIST_COMMON = Makefile.in Makefile.am \
22 It might be cool to generate .texi dependencies by grepping for
23 @include. (If done, it should be done the same way C dependency is
26 Rename --include-deps to --insert-deps?
28 Merge common parts of "dist" targets into dist-local.
30 It would be good to check some parts of GNU standards. Already check
31 for install-sh and mkinstalldirs. What else is required to be in
32 package by GNU standards or by automake?
34 Maybe it should be possible to disable all GNU-specific things with
35 --no-gnu? --ignore-standards? But what? And why?
37 Allow ".h" files to appear in blah_SOURCES; just write them out of
38 existence. [ This is nixed for now because of the auto-dependency
41 automake.in: should ".cc" really -> ".${kr}o"? This doesn't really
42 seem right, but maybe it is so names can be rewritten uniformly? Must
45 look in configure.in's AC_OUTPUT command and include those files in
48 consider auto-including any file that matches "*.in".
49 [ no: po/Makefile.in shouldn't be included ]
51 must look at mkid to see how it works (for subdir usage)
52 [ right now, it doesn't. i don't see a simple fix right now ]
54 Internationalize. [ gettext doesn't have the necessary machinery yet ]
56 ================================================================
59 automatically add its input file to the distribution.
61 Don't hardcode the name of the configuration header. Get it from
62 configure.in (AC_CONFIG_HEADER).
64 Get the list of Makefiles to create from configure.in AC_OUTPUT
66 [ right now we look for any Makefile.am's lying around
67 I think this is better, because it allows use of subdirs
68 which don't use automake -- eg, stuff from gettext ]
70 Should libexec programs have the name transform done on them?
72 Order the output rules sensibly, so FOO_SOURCES and FOO_OBJECTS are
73 together and rules are in the usual order.
75 Make the output minimal: only output definitions for variables that
78 Look at dist's jmake for ideas. [what is this?]
80 Should handle directory hierarchies deeper than 2. Right now there is
81 no support for this at all.
83 ================================================================
87 version.texi handling is broken -- it assumes you only have one .texi
89 (*) In any case, the UPDATED information would be different for
90 each .texi file included in a package -- that is my problem.
91 Now, if no package will ever have more than one .texi file
92 (in a given directory), I can just stop worrying about it.
94 If there is ever more than one, we will need to change the name of
95 'version.texi' to be based on the name of the primary .texi file.
96 Will have to be careful here not to violate MS-DOS name limits. Also
97 will need more than one stamp-vti.
99 [ actually, we could just number them. version0.texi, version1.texi,
102 ================================================================
107 Defined variables, their meanings, and their effects:
110 INCLUDES -I options to cpp
111 CPPFLAGS more cpp flags
113 COMPILE how to compile a C program
114 LINK how to link a C program
116 DIST_SUBDIRS directories which are copied verbatim into the
117 distribution. Used eg for directories holding
118 only example code (which don't have their own
119 makefile). This variable might be a bad idea.
124 ================================================================
128 * Need a way to specify library should be installed
129 * Should support standalone library along with subdir library in same
130 Makefile.am. Maybe: turn off "standalone" mode if library's Makefile.am
131 is not only one specd?
132 * Need a way to install library header files.
133 * Need a way to handle shared libraries.
134 It would be really interesting to be able to easily (as the end-user)
135 make many different versions of the library: shared, static, profiling,