RE: Storing generated files (was: Re: Make cvs ignore some change s in files)

[Brandon Brinkley]

I've heard convincing arguments from both sides on this one, but I consider
it good CM to control the built products for historical/audit purposes.

> >     2)  The generation will not necessarily produce the
> > same result.  A
> > good example is lex/flex and yacc/bison generation.
> > Lex and yacc are
> > different tools on most of the machines on which
> > they occur, yet tend
> > to produce better (and, as I recall, more
> > portable(?!)) results than
> > flex/bison on those systems.  A project I worked on
> > would generate
> > files using lex/yacc on a specific platform and
> > archive them into the
> > sources.  Those building the project would compile,
> > and most would get
> > satisfactory results.  Those who did not could clean
> > out the generated
> > files and rebuild; this usually worked.  We could
> > not require
> > generation of these files, as not all systems had
> > lex/yacc or flex/bison.
> 
> IMHO, this isn't good CM.  If you want developers to
> use the same generated file, they should be using the
> same generation tool.  If this isn't possible, it
> becomes case 3) below.