> what about storing the command used to build a .o file in a '.foo.comm'
> file, and compare it / touch it when building. It wont show up in normal
> 'ls' output, so the 'file listing' doesnt change, and it looks more
> robust.
It takes a lot of work to do this in Makefiles. I don't want to make
that many changes in one patch.
> this also takes care of other command-dependencies, say -D__SMP__, or
> -D__386__, or compiler flags?
It does. Command dependencies are a good thing. They are an expensive
thing, though.
Michael Chastain
<mailto:mec@shout.net>
"love without fear"