160 GNU make
‘mostlyclean’
Like ‘clean’, but may refrain from deleting a few files that people normally
don’t want to recompile. For example, the ‘mostlyclean’ target for GCC does
not delete li/jointfilesconvert/351026/bgcc.a, because recompiling it is rarely necessary and takes a lot
of time.
‘maintainer-clean’
Delete almost everything that can be reconstructed with this Makefile. This
typically includes everything deleted by distclean, plus more: C source files
produced by Bison, tags tables, Info files, and so on.
The reason we say “almost everything” is that running the command ‘make
maintainer-clean’ should not delete configure even if configure can be re-
made using a rule in the Makefile. More generally, ‘make maintainer-clean’
should not delete anything that needs to exist in order to run configure and
then begin to build the program. Also, there is no need to delete parent direc-
tories that were created with ‘mkdir -p’, since they could have existed anyway.
These are the only exceptions; maintainer-clean should delete everything else
that can be rebuilt.
The ‘maintainer-clean’ target is intended to be used by a maintainer of the
package, not by ordinary users. You may need special tools to reconstruct
some of the files that ‘make maintainer-clean’ deletes. Since these files are
normally included in the distribution, we don’t take care to make them easy to
reconstruct. If you find you need to unpack the full distribution again, don’t
blame us.
To help make users aware of this, the commands for the special
maintainer-clean target should start with these two:
@echo ’This command is intended for maintainers to use; it’
@echo ’deletes files that may need special tools to rebuild.’
‘TAGS’ Update a tags table for this program.
‘info’ Generate any Info files needed. The best way to write the rules is as follows:
info: foo.info
foo.info: foo.texi chap1.texi chap2.texi
$(MAKEINFO) $(srcdir)/foo.texi
You must define the variable MAKEINFO in the Makefile. It should run the
makeinfo program, which is part of the Texinfo distribution.
Normally a GNU distribution comes with Info files, and that means the Info
files are present in the source directory. Therefore, the Make rule for an info
file should update it in the source directory. When users build the package,
ordinarily Make will not update the Info files because they will already be up
to date.
‘dvi’
‘html’
‘pdf’
‘ps’ Generate documentation files in the given format. These targets should always
exist, but any or all can be a no-op if the given output format cannot be
Comentários a estes Manuais