On Sunday 22 September 2013 01:34:53 Peter Eisentraut wrote:
> On Thu, 2013-07-25 at 17:07 +0200, Ronan Dunklau wrote:
> > I am using approximatively the layout that was proposed here:
> > http://www.postgresql.org/message-id/51bb1b6e.2070...@dunslane.net
> > It looks like everything is hard-coded
On Thu, 2013-07-25 at 17:07 +0200, Ronan Dunklau wrote:
> I am using approximatively the layout that was proposed here:
> http://www.postgresql.org/message-id/51bb1b6e.2070...@dunslane.net
> It looks like everything is hard-coded to take the source and the
> gcda, gcno files in the base directory,
Thank you for the tip, its done.
2013/7/26 Robert Haas :
> On Thu, Jul 25, 2013 at 11:07 AM, Ronan Dunklau wrote:
>> Hello.
>>
>> I was having trouble figuring how to use the coverage targets when
>> using an extension.
>> I am using approximatively the layout that was proposed here:
>> http://ww
On Thu, Jul 25, 2013 at 11:07 AM, Ronan Dunklau wrote:
> Hello.
>
> I was having trouble figuring how to use the coverage targets when
> using an extension.
> I am using approximatively the layout that was proposed here:
> http://www.postgresql.org/message-id/51bb1b6e.2070...@dunslane.net
> It loo
Please ignore this comment:
> I noticed that make clean leaves gcda and gcov files on the current
> HEAD, and this is no different with the given patch.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
Hello.
I was having trouble figuring how to use the coverage targets when
using an extension.
I am using approximatively the layout that was proposed here:
http://www.postgresql.org/message-id/51bb1b6e.2070...@dunslane.net
It looks like everything is hard-coded to take the source and the
gcda, gcn