On Fri, Jan 29, 2010 at 06:11:34PM -0500, case wrote:
> On Fri, Jan 29, 2010, Ross Walker wrote:
> >
> > clean
> > -----
> > This removes the libraries (.a file) from the lib directory.
>
> This is problematic: NAB is a compiler, and uses some of the .a files in
> amber11/lib to compile programs. If you remove all *.a files in lib, you
> effectively have to recompile NAB after each "make clean".
>
> If there are particular *.a files that should be removed with "make clean",
> you can get rid of those. But "make clean" should not remove all of them.
>
> >
> > distclean
>
> This is probably a bad name for what might be a good target. "distclean"
> implies that you get back to the "distribution" (nothing beyond what was in
> the tar files), but you don't really do that.
>
> But I don't really see the need for this. (1) the test directory can be
> "cleaned" in its own directory; (2) does removing config.h really serve a
> useful purpose?
Yes, it makes cross platform QA testing from one sandbox less error
prone. There is a need for a correct distclean and superclean:
amber has become so big that it is not practical to re-checkout
the tree for nightly testing, and having these targets makes it easy to
have simple and consistent (relative to fast interactive testing and
relative to other software) scripts for QA.
Most of the cleans are standard targets (from googgle):
http://www.ccp4.ac.uk/peter/programming/makefile-targets.html
And imo two additional 2 or 3 line targets at the tail of Makefile
does not increase Amber's software complexity.
The main issue is getting these to do what their standard names imply.
Scott
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Fri Jan 29 2010 - 16:30:04 PST
