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 wrote:
> > Somtimes, it is possible that a code generator replaces the
> > existing files in the code base
> 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 s
Hello Daniel,
>output.h : source.file
> codegen -o output.h-tmp source.file
The code gen being used is a graphical program which cannot be
configured through the terminal.
> diff output.h output.h-tmp >/dev/null || mv output.h-tmp output.h
> rm -f output.h-tmp
Is there a way t
On Mon, 13 Feb 2012, Raman Gopalan wrote:
Also, do you suggest a work around?
Something like this?
output.h : source.file
codegen -o output.h-tmp source.file
diff output.h output.h-tmp >/dev/null || mv output.h-tmp output.h
rm -f output.h-tmp
?
(untested)
- Daniel
_
Hello Lawrence,
Thanks for the reply.
>This looks like work for your code generator instead of make.
I agree with you. This should be fixed in the code gen. But I'm
currently working with a production code generator (DAVE)
which is nor free and does not include this feature. The build
proces
This looks like work for your code generator instead of make. The code
generator could do a diff before replacing the file.
Make would have to keep a backup copy of the last time it built with that file,
increasing complexity and time for normal builds.
I'd recommend against this.
-- Lawrence
