| |
In lugnet.cad.dev, Sproaticus wrote:
> Steve Bliss wrote:
> > In lugnet.cad.dev, Todd Lehman wrote:
> > > I'm not super-duper POV-fluent, but if anyone wants to make POV-rendered
> > > versions of the LDraw parts, I can stick 'em in the partsref as an alternate
> > > view, if that's OK with Steve.
> > That's fine with me. The only downside is applying updates. When new parts are
> > released for LDraw, I don't update individual partsref images and pages, I just
> > regenerate the whole shebang. So any manual edits would probably get
> > overwritten. Anyone got a good idea on avoiding this?
>
> Are you familiar with the make utility? It allows you to describe an
> arbitrary set of modules, with their associated interdependencies, and then
> re-build only the modules which have changed and modules dependant upon them.
Yep, I'm familiar with make. I even went to look for one once. Do you know how
hard it is to search the net for 'make'? I never could figure out a decent set
of search-words...
Oh, wait. I've got a make.exe with my old copy of Turbo Pascal. And another
with GNAT-Ada. Hmmm... Nope, no docs on either.
Anyone got make docs?
One problem with make is that sometimes, the image file will be based on an
outdated DAT, but the image will still have a more recent datestamp than the
current DAT. And make can't deal with that (unless someone changed make and
didn't tell me).
For example, I wrote a part-file. It's released in an update. After the new
update goes out, I notice a problem, and submit a fixed file. The fixed file
won't be released until the following update, which could be a month or more.
In the meantime, I install the just-released update, rebuild partsref using
make. An image file is generated for the new part. When the next update is
released, it will have the fixed file, but the datestamp on the fixed DAT will
be older than the datestamp on the image.
> Of course, using make would require that you can build each image and html
> file from the command-line, one at a time.
Which is not a big deal, in terms of how long it will take to process, if only
the *changed* files are being updated.
One problem would be if make isn't smart enough to wait until the rendering
program completes, which is a problem if the rendering program is Windows-based.
Steve
|
|
Message has 3 Replies:
Message is in Reply To:
32 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
|
|
|
|
