Re: Ignoring some binaries generated in src/test - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Ignoring some binaries generated in src/test
Date
Msg-id CAB7nPqRkXigX8fkALzsGVikZJHrBOT2_o33=aDC50NosmNOSBw@mail.gmail.com
Whole thread Raw
In response to Re: Ignoring some binaries generated in src/test  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Apr 25, 2015 at 6:14 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> Tom Lane wrote:
>>> The current logic in src/test/Makefile, particularly the way that
>>> the modules subdirectory is handled, seems pretty ugly/convoluted
>>> anyway.  I wonder why it was done that way rather than just ensuring
>>> that modules/ doesn't do anything for "make install"?
>
>> Because we do want to have the Makefile in src/test/modules to install
>> the modules if "make install" is invoked there.  That way, you can run
>> "make -C src/test/modules install installcheck", and it works.
>
> OK.  I still wonder if there isn't a better way to get that effect, but
> I left it alone for now.  I committed Michael's new .gitignore files and
> fixed the Makefiles so that "make clean" and friends clean up properly.

Thanks.
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: collate.linux.utf8 test coverage
Next
From: Michael Paquier
Date:
Subject: Re: forward vs backward slashes in msvc build code