Hi all,
I've noticed that parts of the AMBER compilation and testing create a
lot of files which are not taken care of by "make clean". I'm especially
talking about the output files from many of the tests, and directories
such as bin/, include/ and lib/ together with all their contents.
Is this a deliberate choice, or is it left over from somewhere, and
would people be happy if I began work to fix it (e.g., creation of
cleaning scripts)? It seems to me that, ideally, a "make clean" should
restore the cleaned directory to its original state, with the exception
of configuration files such as config.h and config_amber.h. But I
wouldn't be surprised to discover that there's a reason why things have
been done the way they have in AMBER. Thoughts?
Thanks,
Ben
--
Benjamin P. Roberts
Postdoctoral Research Associate
Quantum Theory Project
University of Florida
2301 New Physics Building #92
PO Box 118435
Gainesville FL 32611-8435
USA
Phone: +1 352 392 6712
Cell: +1 352 222 3677
Member of the Royal Australian Chemical Institute
and of the American Chemical Society
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Fri Aug 21 2009 - 08:11:05 PDT
