Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!tut.cis.ohio-state.edu!ucbvax!ANDREW.CMU.EDU!ghoti+ From: ghoti+@ANDREW.CMU.EDU (Adam Stoller) Newsgroups: comp.soft-sys.andrew Subject: Re: collection of .dog files Message-ID: Date: 29 Jan 91 13:10:35 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 27 Excerpts from internet.info-andrew: 28-Jan-91 collection of .dog files Bill Janssen@parc.xerox. (328) > I've found the .dog files generated during the build process of Andrew > to be quite handy. They'd be even handier if they were collected in > some standard place so that everyone can find them. I'd like to suggest > we create the directory ${ANDREWDIR}/dog/, and put all of them in there > during the install phase. > Comments? > Bill Handy for what? - We generally use them for debugging - in which case we prefer them to be in the directory in which they were built (so that both source and [dynamic]object files are together which makes it easier to debug. Also - I believe they act as a form of timestamp for the make process - and installing them elsewhere, without removing them from their built location becomes a tremendous overhead in space allocation. Of course it could be done with symlinks - but back to my original question - what do you find them handy for that you think they would be handier if put together? --fish