To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 3407
3406  |  3408
Subject: 
Re: Partsref is Moving to LUGNET
Newsgroups: 
lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray
Date: 
Thu, 2 Dec 1999 19:40:16 GMT
Viewed: 
3545 times
  
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:
  Re: Partsref is Moving to LUGNET
 
(...) You could try the version which comes with Cynwin32: (URL) used Beta 20.1; it seems pretty stable. If you're not too keen on using the Unix sub-layer (slow), try dmake: (URL) it seems to have gone commercial -- you have to *pay* for the (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
  Re: Partsref is Moving to LUGNET
 
(...) This is kludgy but might work. Details left as an exercise. Your problem is that what you want is to know when a file is *new to YOU* not what it's timestamp is. Keep two complete sets of .dat files. One is an image of the state of files, but (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
  Re: Partsref is Moving to LUGNET
 
Steve Bliss wrote in message ... [ ... snip ... ] (...) There is a very good Make book available from O'Reilly & Associates, _Managing Software Projects with Make_. I have found that this book always seems to have an example for something I was (...) (25 years ago, 7-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)

Message is in Reply To:
  Re: Partsref is Moving to LUGNET
 
(...) 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. Of course, using (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)

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
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR