Re: automake 1.12.1 changes extension of bison-generated header files

2012-09-15 Thread Stefano Lattarini
On 09/15/2012 03:06 AM, Matt Turner wrote: > I started thinking about this again recently, so I thought I'd respond. > > So, first thanks for the email and the suggestion. > > On Sat, Jul 14, 2012 at 1:42 AM, Stefano Lattarini > wrote: >> On 07/13/2012 07:16 PM, Matt Turner wrote: >>> Hi, >>> >>

Re: automake 1.12.1 changes extension of bison-generated header files

2012-09-14 Thread Matt Turner
I started thinking about this again recently, so I thought I'd respond. So, first thanks for the email and the suggestion. On Sat, Jul 14, 2012 at 1:42 AM, Stefano Lattarini wrote: > On 07/13/2012 07:16 PM, Matt Turner wrote: >> Hi, >> >> In Mesa (http://www.mesa3d.org/) we generate some C++ cod

Re: automake 1.12.1 changes extension of bison-generated header files

2012-07-14 Thread Stefano Lattarini
On 07/13/2012 07:16 PM, Matt Turner wrote: > Hi, > > In Mesa (http://www.mesa3d.org/) we generate some C++ code using > Bison. The input is glsl_parser.yy and automake-1.11 and prior > versions generated glsl_parser.h. 1.12 generates glsl_parser.hh, and > if the input file is named .ypp it generat

automake 1.12.1 changes extension of bison-generated header files

2012-07-13 Thread Matt Turner
Hi, In Mesa (http://www.mesa3d.org/) we generate some C++ code using Bison. The input is glsl_parser.yy and automake-1.11 and prior versions generated glsl_parser.h. 1.12 generates glsl_parser.hh, and if the input file is named .ypp it generates a .hpp file. How can we configure our build system s