Subject:
|
Re: pictures at tracker
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Thu, 16 May 2002 03:33:34 GMT
|
Viewed:
|
761 times
|
| |
|
|
In lugnet.cad, Steve Bliss writes:
> In lugnet.cad, Larry Pieniazek writes:
>
> > Hey... this is starting to sound like build/make dependency analysis. Any
> > chance of getting good old "make" itself to do the work of figuring out what
> > needs to be regenned when a file is uploaded?
>
> That seems reasonable. The dependencies are fairly straightforward, and can
> be checked by simple mod-date comparision.
>
> > The dependency calculation seems straightforward (just scan the file to find
> > first level dependencies) and the various dirs seem a lot like include path
> > analysis...
>
> Hmm. Can it deal with files being in subdirectories? Like, if the search
> path is /home/tracker/unofficial;/home/tracker/official, and the directory
> structure is:
>
> /home
> /tracker
> /official
> /p
> /48
> /parts
> /s
> /unofficial
> /p
> /48
> /parts
> /s
>
> Can make find stud.dat under the right /p/ directory?
Well, not sure. Bear with.
Remember that make doesn't actually make things. Or find things. It just
uses other programs to make them or find them based on production rules. In
this case it's actually LDGlite that needs to find the correct stud.dat
"thing", right? So IT needs to know to check in multiple places (which no
tool currently does, they all expect to find things in certain places, right?)
But in the past, IIRC from my olden days, when we were using a tool that did
not understand include file path checking, we would use make to create an
*image* of the directories (by creating symbolic links not by copying the
actual files) that we wanted with the correct (as in, newest or most
correct) files "extracted" (symlinked, really) to the image. Or at least I
think we did.
I am not an expert on production rules. (the rules that say "to make an X
you run Zee against a Y" sort of rules) But I seem to recall magic that
built the symlinks via production rules that ran against dependencies and
looked for things, and other magic that generated the dependencies by
examining the sourcefiles and the things they referenced.
This is also sort of "source code control"ish... Official and Unofficial are
like different branches in a source tree... or something like that. When you
get an image to build with from a source code control system (like PVCS, VSS
or SCCS) what you get are all the files needed, taken from the correct
branches based on what you said (newest, newest that has been tested, a
certain baseline release, whatever)
What platform is the box? Linux? If so you may be all set because Linux
supports symlinks and has a pretty powerful make, I thought (doesn't it use
gnumake???) It also has SCCS, right? Or at least RCS? Those may help too.
|
|
Message has 2 Replies:
 | | Re: pictures at tracker
|
| (...) Actually, when it does it's timestamp comparisons to decide if things need to be made, it *does* need to find them. See my other post. -Kyle (23 years ago, 16-May-02, to lugnet.cad)
| | | RE: pictures at tracker
|
| Larry Wrote: (...) This is the key point - if ldglite needs to have things in certain places in order to work correctly, the output of our make sessions needs to set up that structure correctly. (...) Yes, symlinks are super-powerful (and (...) (23 years ago, 16-May-02, to lugnet.cad)
|
Message is in Reply To:
| | Re: pictures at tracker
|
| (...) That seems reasonable. The dependencies are fairly straightforward, and can be checked by simple mod-date comparision. (...) Hmm. Can it deal with files being in subdirectories? Like, if the search path is /home/tracker/unoffi.../official, and (...) (23 years ago, 16-May-02, to lugnet.cad)
|
77 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
