Closed tbastos closed 4 years ago
Thanks for the hint!
I agree :)
While I did get cpp-coveralls to work, I had to duplicate a significant amount of effort I already put into LCOV (for local static HTML coverage reports). I ended up writing my own LCOV-based submitter (Lcoverals), but there are a few others available too.
Perhaps the best (or least?) thing to do is just add a couple of the alternatives (especially those based on LCOV) to the https://coveralls.io/docs/cpp page.
Cheers.
Well, to push my own project, there's kcov:
https://github.com/SimonKagstrom/kcov
where you can generate and upload coverage for C/C++/Rust/Python/Bash with
kcov --coveralls-id=$TRAVIS_JOB_ID /path/to/outdir executable
(or without travis with the repo token).
This issue has been automatically marked for closure because it has not had recent activity. It will be closed if no further activity occurs. If your issue is still active please add a comment and we’ll review as soon as we can. Thank you for your contributions.
This is a very old issue, but just in case there's someone searching for this same info...
First. some background:
lcov
is one.Your task in using one of the official integrations is to get your C/C++ coverage into that lcov
format.
For help with that, check out these two resources:
After wasting many hours trying to make "cpp-coveralls" work for my project, I gave up and looked into alternatives based on lcov. And indeed the lcov route is both easier and significantly more powerful. I suggest you update the C/C++ doc to reflect this observation...
Instead of using
cpp-coveralls
(a new front-end for gcov with coveralls integration), any native GCC project (in c/c++/objective-c) is better off usinglcov
(a mature front-end for gcov) and then either of these tools to upload the lcov file to coveralls: