Hi all,
I have added the following information to the HACKING file. Hope it
is useful to you.
* Make Targets
As the Makefiles are generated by autoconf/automake, they provides
the standard targets specified in the GNU Coding Standard. We
describe some of the more useful ones here.
** clean
A "make clean" will remove all files generated by "make all".
Do this when you need a clean build.
** maintainer-clean
A "make maintainer-clean" will remove all generated files,
including those that comes with the distribution (e.g. Makefiles,
configure, etc). Normally you do not need to do a maintainer-clean.
All you need is to modify the sources of the generated files, and
the targets will be regenerated by make. Do a maintainer-clean only
if you have all the tools mentioned in the previous section (you don't
need cvs2cl.pl unless you are doing a "make dist" or a "make
distcheck").
** check
A "make check" will run all the regression test scripts. Do this
after you make changes assures that you haven't broken anything.
** tags/TAGS
A "make tags" or "make TAGS" will run GNU etag to generate TAGS
files (i.e. cross-reference databases) for all subdirectories.
You can then use the GNU emacs editor to navigate the code base.
** dist
A "make dist" will create a tarball of the distribution. The ChangeLog
file is generated by cvs2cl.pl. Therefore, you will need to install
the Perl script if you are doing a "make dist" from a CVS checkout
or if you "make dist" after "make maintainer-clean".
** distcheck
A "make dist" will create a tarball of the distribution, test if
installation and uninstallation is okay, and run the test scripts.
Philip
* Philip W. L. Fong
* pw...@us...
|
