Re: gram.y => preproc.y - Mailing list pgsql-hackers

From Tom Lane
Subject Re: gram.y => preproc.y
Date
Msg-id 21345.1226607004@sss.pgh.pa.us
Whole thread Raw
In response to gram.y => preproc.y  (Michael Meskes <meskes@postgresql.org>)
Responses Re: gram.y => preproc.y  (Michael Meskes <meskes@postgresql.org>)
Re: gram.y => preproc.y  (Michael Meskes <meskes@postgresql.org>)
List pgsql-hackers
Michael Meskes <meskes@postgresql.org> writes:
> since my last email seems to have disappeared, here we go again. Here's my
> current patch that includes the changes to the build system. Thanks to Magnus
> for the Windows part.

> Comments anyone? 

+ $(srcdir)/preproc.y: $(top_srcdir)/src/backend/parser/gram.y
+     perl parse.pl < $< > $@ 

Use $(PERL) here.

(I'm not sure about the equivalent in the Windows world; it looks like
there are already places in Solution.pm that invoke perl via just
system("perl ..."), but is that really a good idea?  Anyway, not
directly your problem.)
 clean distclean:
!     rm -f keywords.c *.o ecpg$(X) preproc.y

Actually, we want to fix it so that preproc.y is treated like preproc.c,
ie, it's part of the shipped tarballs even though it's no longer in CVS.
For the same reason, you want to generate it in $(srcdir) even in a
VPATH build.  (Parts of this patch have that right and part don't.
You might want to test in a VPATH build before committing.)

Can't comment on the MSVC change.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Block-level CRC checks
Next
From: Tom Lane
Date:
Subject: Re: Simple postgresql.conf wizard