[Mesa-dev] Flex and bison generated files in revision control

Ian Romanick idr at freedesktop.org
Fri Feb 11 16:53:21 PST 2011

Hash: SHA1

On 01/31/2011 03:46 PM, Ian Romanick wrote:
> Tracking files generated by flex and bison puts an undue burden on
> people doing work on the various parers and lexers in Mesa.
> Tracking files generated by flex and bison generates extraneous noise in
> commit logs.
> Tracking files generated by flex and bison makes cherry-picking fixes
> from the development branch back to stable branches more difficult than
> it needs to be.
> Tracking files generated by flex and bison is a just plain bad idea.
> Flex and bison have working ports for every platform on which we support
> building Mesa.  It even works when building projects from within Visual
> Studio (http://msdn.microsoft.com/en-us/library/aa730877%28vs.80%29.aspx).
> I have just pused a branch called flex-and-bison-required that removes
> these files.  What still needs to be done in that branch:
>   - Generate the files that have been removed during tarball creation.
>   - Checks for flex and bison in configure.ac.
>   - Fixes for your platform.  If this branch does not work
> out-of-the-box on your platform, push fixes.
> On March 1st (or sooner with consensus) this branch will be merged to
> master.

I think the branch is ready.  The bits to generate the parser and lexer
files during tarball creation are a big, ugly hack.  I'm open to
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/


More information about the mesa-dev mailing list