Re: Makefile for parser

Поиск
Список
Период
Сортировка
От Thomas Lockhart
Тема Re: Makefile for parser
Дата
Msg-id 395802D8.71865EC7@alumni.caltech.edu
обсуждение исходный текст
Ответ на Makefile for parser  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
Ответы Re: Makefile for parser  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
> > I've started doing a bit of work on gram.y, and am noticing some new
> > cruftiness in the Makefile: if I add tokens to gram.y/keywords.c 
> > then I can't just remake in that directory since parse.h is not 
> > updated elsewhere in the tree.
> Uh ... what's your point?  If the changes to parse.h affect anything
> else then you ought to be doing a top-level make --- or at the very
> least a make in src/backend --- and that will rebuild
> include/parser/parse.h.

Any change to gram.y regenerates the local copy of parse.h and affects
other files *in that local directory* (as well as elsewhere). The
makefile *in that local directory* should be able to make the other
files *in that same directory* at the same time.

That's my point ;)

istm that the local makefile should at least reach up and over to the
other rule for building parse.h (wherever that is), so that parse.h gets
moved to the include/ area. If make is invoked from the top of the tree,
then it is a noop. If make is invoked from backend/parser/, then the
local files get rebuilt correctly.
                    - Tom


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Is *that* why debugging backend startup is so hard!?
Следующее
От: "Mikheev, Vadim"
Дата:
Сообщение: RE: Big 7.1 open items