Re: flex/bison output wrongly created in the source directory

On Jan 9, 2008 9:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Warren Turkal" <wturkal(at)gmail(dot)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.

That makes sense.

> 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.

I was not building multiple builds in parallel as I thought they might
get fouled by the different builds. Since they do appear to not
change, I think they are just fine. Thanks for the help!

wt