Attachment 87941 Details for Bug 48821 – [03/11] lcov.am: fix to work in out-of-tree builds

[patch] [03/11] lcov.am: fix to work in out-of-tree builds

0003-lcov.am-fix-to-work-in-out-of-tree-builds.patch (text/plain), 1.27 KB, created by Simon McVittie on 2013-10-21 17:27:25 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2013-10-21 17:27:25 UTC

Size: 1.27 KB

patch

obsolete

>From 83ce6c6dd8ab030bc109c6d27c5c07a755d88dac Mon Sep 17 00:00:00 2001
>From: Simon McVittie <simon.mcvittie@collabora.co.uk>
>Date: Tue, 17 Apr 2012 15:30:35 +0100
>Subject: [PATCH 03/11] lcov.am: fix to work in out-of-tree builds
>
>Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
>---
> tools/lcov.am | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
>diff --git a/tools/lcov.am b/tools/lcov.am
>index 95c4393..488ab1e 100644
>--- a/tools/lcov.am
>+++ b/tools/lcov.am
>@@ -22,12 +22,14 @@
> # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
> 
> lcov-reset:
>-	lcov --directory @top_srcdir@ --zerocounters
>+	lcov --base-directory @top_srcdir@ --directory @top_builddir@ \
>+		--zerocounters
> 
> lcov-report:
>-	lcov --directory @top_srcdir@ --capture \
>-		--output-file @top_builddir@/lcov.info.tmp
>-	lcov --directory @top_srcdir@ --output-file @top_builddir@/lcov.info \
>+	lcov --base-directory @top_srcdir@/dbus --directory @top_builddir@ \
>+		--capture --output-file @top_builddir@/lcov.info.tmp
>+	lcov --base-directory @top_srcdir@/dbus --directory @top_builddir@ \
>+		--output-file @top_builddir@/lcov.info \
> 		--remove @top_builddir@/lcov.info.tmp '*-scan.c'
> 	rm @top_builddir@/lcov.info.tmp
> 	$(mkdir_p) @top_builddir@/lcov.html
>-- 
>1.8.4.rc3
>

Actions: View | Splinter Review

Attachments on bug 48821: 60172 | 60173 | 60174 | 87939 | 87940 | 87941 | 87942 | 87943 | 87944 | 87945 | 87946 | 87947 | 87948 | 87949

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.