janssen@parc.xerox.com (Bill Janssen) (01/29/91)
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
ghoti+@ANDREW.CMU.EDU (Adam Stoller) (01/29/91)
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
wdc@ATHENA.MIT.EDU (Bill Cattey) (01/30/91)
Excerpts from mail: 28-Jan-91 collection of .dog files Bill Janssen@parc.xerox. (328) > I'd like to suggest we create the directory ${ANDREWDIR}/dog/, and put > all of them in there during the install phase. I think it would be a good option to have. However I would like to have it be OPTIONAL. Right now I am very comfortable having my developers attach my build tree, and my users not use the .dog files. I have a hard enough time talking my systems people out of 30 MEG per platform to export an Andrew NFS filesystem. Adding in the dog files by default would result in my having to remove them from the destination directory by hand. -wdc
janssen@parc.xerox.com (Bill Janssen) (01/30/91)
Perhaps there should be another define or two in the config files to say whether to move them, and if so, where. Bill