Ken MacDonald wrote:
> Nathan Kidd wrote:
>> ...then teach your build system to build targets only when sources
>> have changed.
>
> Teaching your build system to build targets when they have changed is
> non-trivial. You not only have to worry about the file itself
> changing, but whether its 'include' files have changed, or include
> files that are included by the include files, and so on. Also,
> changing options in a Makefile may require rebuilding targets as well
> even if the source code itself is unchanged. I worked for some time
> in a ClearCase-oriented environment, and their 'clearmake' product
> does a fine job of build-avoidance, but is a fairly complex piece of
> s/w. FWIW, Ken
If someone is running builds I sure hope they understand this. But it's
not like this is somthing new or that difficult either (make *has* been
around since the 70's). Variants of make, or ant, or Scons, or (as
suggested by the OP's use of "solutions") MSdev all can automate this
robustly.
-Nathan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 9 18:07:09 2007