RE: Scheduling lcov code coverage script

Hi,

I tried doing a custom do_autoconf,but ran into other issues. Anyway,
sounds like you pretty much got things working by now
with 'lcov-report.sh -f',so perhaps i should just back off now
;)

Maarten
From: Norbert Thiebaud
Sent: 10-12-2014 10:35
To: Maarten Hoes
Cc: libreoffice-dev
Subject: Re: Scheduling lcov code coverage script
On Wed, Dec 10, 2014 at 3:16 AM, Maarten Hoes <hoes.maarten@gmail.com> wrote:
> Hrm.
>
>
> It appears I get the openldap build error when I do the build like this
> (like it happens with the tb script) :
>
> $ LDFLAGS+='-fprofile-arcs'
> $ CFLAGS+='-fprofile-arcs -ftest-coverage'
> $ CXXFLAGS+='-fprofile-arcs -ftest-coverage'
> $ CPPFLAGS+='-fprofile-arcs -ftest-coverage'
> $ export LDFLAGS CFLAGS CXXFLAGS CPPFLAGS
> $ ./autogen.sh --enable-python=internal --disable-online-update
> --without-system-libs --without-system-headers
> $ make build-nocheck
>
>
>
> But not when I do the build like this (like I do on the cmdline, or is done
> in the lcov-report.sh script) :
>
> $ LDFLAGS+='-fprofile-arcs' CFLAGS+='-fprofile-arcs -ftest-coverage'
> CXXFLAGS+='-fprofile-arcs -ftest-coverage' \
> CPPFLAGS+='-fprofile-arcs -ftest-coverage' ./autogen.sh
> --enable-python=internal --disable-online-update \
> --without-system-libs --without-system-headers
> $ make build-nocheck

then the easiest work around is to define a custom phase for that
profile that overide the configure (aka autogen) step
so that it does it the second way (and remove the *FLAGS from the
profile's config

Norbert