2 * Handle installable libraries and headers
5 * clean targets not very well tested
7 Should 'distclean' remove $(SCRIPTS)?
8 Should 'maintainer-clean' do "rm -rf .deps"?
9 Should look for clean-local targets in Makefile.am.
11 Consider a --install-missing option to install missing files such as
12 mdate-sh, texinfo.tex, etc.
14 Think about writing a small tool to guess what the local Makefile.am
17 Prettyprint macro definitions, eg:
18 DIST_COMMON = Makefile.in Makefile.am \
21 It might be cool to generate .texi dependencies by grepping for
22 @include. (If done, it should be done the same way C dependency is
25 Rename --include-deps to --insert-deps?
27 Merge common parts of "dist" targets into dist-local.
29 It would be good to check some parts of GNU standards. Already check
30 for install-sh and mkinstalldirs. What else is required to be in
31 package by GNU standards or by automake?
33 Maybe it should be possible to disable all GNU-specific things with
34 --no-gnu? --ignore-standards? But what? And why?
36 Allow ".h" files to appear in blah_SOURCES; just write them out of
37 existence. [ This is nixed for now because of the auto-dependency
40 automake.in: should ".cc" really -> ".${kr}o"? This doesn't really
41 seem right, but maybe it is so names can be rewritten uniformly? Must
44 look in configure.in's AC_OUTPUT command and include those files in
47 Auto-distribute "ChangeLog.[0-9]+"?
49 consider auto-including any file that matches "*.in".
50 [ no: po/Makefile.in shouldn't be included ]
52 must look at mkid to see how it works (for subdir usage)
53 [ right now, it doesn't. i don't see a simple fix right now ]
55 Internationalize. [ gettext doesn't have the necessary machinery yet ]
57 ================================================================
60 automatically add its input file to the distribution.
62 Don't hardcode the name of the configuration header. Get it from
63 configure.in (AC_CONFIG_HEADER).
65 Get the list of Makefiles to create from configure.in AC_OUTPUT
67 [ right now we look for any Makefile.am's lying around
68 I think this is better, because it allows use of subdirs
69 which don't use automake -- eg, stuff from gettext ]
71 Should libexec programs have the name transform done on them?
73 Order the output rules sensibly, so FOO_SOURCES and FOO_OBJECTS are
74 together and rules are in the usual order.
76 Make the output minimal: only output definitions for variables that
79 Look at dist's jmake for ideas. [what is this?]
81 Should handle directory hierarchies deeper than 2. Right now there is
82 no support for this at all.
84 ================================================================
88 version.texi handling is broken -- it assumes you only have one .texi
90 (*) In any case, the UPDATED information would be different for
91 each .texi file included in a package -- that is my problem.
92 Now, if no package will ever have more than one .texi file
93 (in a given directory), I can just stop worrying about it.
95 If there is ever more than one, we will need to change the name of
96 'version.texi' to be based on the name of the primary .texi file.
97 Will have to be careful here not to violate MS-DOS name limits. Also
98 will need more than one stamp-vti.
100 [ actually, we could just number them. version0.texi, version1.texi,
103 ================================================================
108 Defined variables, their meanings, and their effects:
111 INCLUDES -I options to cpp
112 CPPFLAGS more cpp flags
114 COMPILE how to compile a C program
115 LINK how to link a C program
117 DIST_SUBDIRS directories which are copied verbatim into the
118 distribution. Used eg for directories holding
119 only example code (which don't have their own
120 makefile). This variable might be a bad idea.
127 lib_LIBADD code conditionally included in a library
128 This probably needs to be redone anyway.
130 AM_TEXINFOS override form
131 SUFFIXES additional suffixes
133 ================================================================
137 * Need a way to specify library should be installed
138 * Should support standalone library along with subdir library in same
139 Makefile.am. Maybe: turn off "standalone" mode if library's Makefile.am
140 is not only one specd?
141 * Need a way to install library header files.
142 * Need a way to handle shared libraries.
143 It would be really interesting to be able to easily (as the end-user)
144 make many different versions of the library: shared, static, profiling,
147 Some examples to keep in mind while doing this: