norman@d.cs.okstate.edu (Norman Graham) (10/30/90)
[This is posting number two for this note. I'm posting it again because
I never saw the original and I never got any responces. Sorry if you've
seen it before.]
I'm solicting advice on how makefiles should manipulate Projector
projects. If you have a good strategy for using Make with Projector,
please drop me a note; I'll post a summary of suggestions in a couple
of weeks.
The following is an example of the kinds of things I'm after:
The most simple compilation strategy would be to (1) have the Makefile
check out read-only copies of all the sources not already checked out,
(2) then have the Makefile proceed as normal, (3) and then delete all
the sources that the Makefile checked out.
I'm sure some of you have methods that automate the following tasks;
I hope you'll take a few moments to share them. (By 'files' I mean
points in a revision tree as maintained by Projector):
- printing files modified after a given date
- printing files that have changed after the last printing
- backing up a project
- rebuilding a particular version of the target program
- maintaining object directories and libraries
- extracting change comments for all files changed after a given date
- keeping up with each revision that belongs to a particular version
of the target program
- etc.
Yours,
Norm
--
Norman Graham <norman@a.cs.okstate.edu> {cbosgd,rutgers}!okstate!norman
The opinions expressed herein do not necessarily reflect the views of
the state of Oklahoma, Oklahoma State University, OSU's Department of
Computer Science, or of the writer himself.