| |
Steve Bliss wrote:
> 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...
You could try the version which comes with Cynwin32:
http://sourceware.cygnus.com/cygwin/
I've used Beta 20.1; it seems pretty stable. If you're not too keen on using
the Unix sub-layer (slow), try dmake:
http://www.wticorp.com/dmake/
Hmmm, it seems to have gone commercial -- you have to *pay* for the binaries.
Arg. Well, if you don't mind paying homage to the Great Redmond Satan,
there's always Microsoft NMake:
ftp://ftp.microsoft.com/Softlib/MSLFILES/nmake15.exe
> Anyone got make docs?
For GNU make:
http://www.delorie.com/gnu/docs/make/make_toc.html
> 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.
You'd get this in any situation where you mix your development environment
with your everyday environment.
One alternative is to put a rule into your makefile, e.g. "clean", which will
delete all output image files. But this sorta defeats the purpose of using a
makefile.
> > 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.
Oh. Yah, that'd be a problem.
Within the shell that comes with WinNT 4.0 anyway, you can go "start /wait
ldlite somedat.dat", and the shell will wait for the process to end. I don't
know if this works on Win95/98.
Cheers,
- jsproat
--
Jeremy H. Sproat <jsproat@io.com> ~~~ http://www.io.com/~jsproat/
Arthur, I have POCKETS!!!
|
|
Message has 1 Reply:
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
|
|
|
|
