Re: flex/bison output wrongly created in the source directory - Mailing list pgsql-hackers

From Tom Lane
Subject Re: flex/bison output wrongly created in the source directory
Date
Msg-id 25931.1199944286@sss.pgh.pa.us
Whole thread Raw
In response to flex/bison output wrongly created in the source directory  ("Warren Turkal" <wturkal@gmail.com>)
Responses Re: flex/bison output wrongly created in the source directory  ("Warren Turkal" <wturkal@gmail.com>)
Re: flex/bison output wrongly created in the source directory  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
"Warren Turkal" <wturkal@gmail.com> writes:
> I was wondering if there is a reason that the flex and bison and other
> generated source files end up in the source directory when doing an
> out-of-tree build. Would a patch that puts those files in the build
> trees be accepted?

Probably not, since our intention is that those files be distributed as
part of source tarballs.

Also, since they are (or should be) architecture-independent, what's the
point?  Out-of-tree builds are intended to support building for multiple
architectures in parallel; but there's no reason to force independent
reconstructions of these common derived files.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Warren Turkal"
Date:
Subject: Re: operator suggest " interval / interval = numeric"
Next
From: Tom Lane
Date:
Subject: Re: operator suggest " interval / interval = numeric"