On Sun, Aug 10, 2014 at 1:10 AM, Marko Käning wrote:
> Hi Ben,
Hi Marko,
>
> On 09 Aug 2014, at 15:07 , Ben Cooksley wrote:
>> Is lcov available for OS X?
>
> I haven’t checked that up to now. Do we need that? How can I check it?
Long term, it will be needed as lcov is used for code coverage c
Hi Ben,
On 09 Aug 2014, at 15:07 , Ben Cooksley wrote:
> Is lcov available for OS X?
I haven’t checked that up to now. Do we need that? How can I check it?
> This is a part of our CI implementation as an optional feature, which
> it appears plasma-framework has enabled.
Oh, I see, I saw somew
On Sun, Aug 10, 2014 at 1:05 AM, Marko Käning wrote:
> Hi Aleix,
Hi Marko,
>
> On 08 Aug 2014, at 01:27 , Aleix Pol wrote:
>> You're building with coverage enabled, I guess you're using the same build
>> arguments as Jenkins?
>
> that’s what I figured, but I wonder why this never happened befo
Hi Aleix,
On 08 Aug 2014, at 01:27 , Aleix Pol wrote:
> You're building with coverage enabled, I guess you're using the same build
> arguments as Jenkins?
that’s what I figured, but I wonder why this never happened before. Something
must have changed in the meantime.
Yes, I should be using the
On Fri, Aug 8, 2014 at 12:06 AM, Marko Käning wrote:
> What am I missing here?
>
> ---
> ld: library not found for -lgcov
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> ---
>
> This hasn’t happened before...
>
You're building with coverage enabled, I guess
What am I missing here?
---
ld: library not found for -lgcov
clang: error: linker command failed with exit code 1 (use -v to see invocation)
---
This hasn’t happened before...
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://ma
