Hello Edward, Thanks for the mail. I have tried using git for this task. It works fine for my needs.
Thanks for the tip. Regards, Raman On Tue, Feb 14, 2012 at 3:25 PM, Edward Welbourne <e...@opera.com> wrote: > > Somtimes, it is possible that a code generator replaces the > > existing files in the code base with the same content. It might > > be a good option to enable content checking before make > > rebuilds the replaced file (with the same content) again. > > Another approach: have the code generator run on a source tree separate > from the one in which you run make; use rsync or some similar tool to > synchronise your build tree with this source tree; configure the > synchroniser to only copy what's changed, regardless of time-stamps; > ISTR rsync can be persuaded to do that, but git would work for this job, > equally. > > Now your code-gen can be profligate about rewriting and make need only > concern itself with time-stamps. Keeping track of the "do nothing > unless changed" problem is delegated to the synchroniser. Your build > process is then: run the graphical monstrosity; sync its tree with the > build tree; run make. > > The unix philosophy: each tool does one job well; chain such tools, to > do complex jobs, > > Eddy. >
_______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
