-
|
Hey everyone, I am using windows, where lcov is not available,, is there a way to still use the integration? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
|
@makas005 Thanks for the question, tagging @TSonono who contributed that feature. It seems like based on your testing we may need to fill a gap to support this for you, but I'll let @TSonono fill any knowledge gaps here. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @makas005 and @gcampbell-msft , Yes indeed the test coverage integration in CMake Tools currently only supports lcov based coverage data. The reason I only added support for that in the implementation I did, is that it's the only coverage data format that I'm familiar with myself. As specified in the #4094, I think adding support for additional coverage data formats would be a good thing. Very small adjustments would have to be done to the current implementation (in addition to the work of actually parsing different coverage data types) for this to be possible. However, I can't comment the extent of the parsing work, since I'm not familiar with (what I assume you are using) MSVC's coverage data format. It might perhaps be proprietary, which would make it more difficult if there are no existing parsers for it written in typescript/javascript (as was the case with lcov).
Assuming you are using a compilation toolchain (that is not MSVC) that supports gcov output (such as
|
Beta Was this translation helpful? Give feedback.
-
|
Hey @TSonono, thank you for your quick reply! I understand that this is a rather rase use-case and may not be addressed. Switching to linux would make things much easier, but unfortunately this is not possible at the moment. Using the windows port of lcov also comes with problems, but this might the most promising solution at the moment. Thank you! |
Beta Was this translation helpful? Give feedback.
-
I agree that this could have been nice. The problem with this approach is that there are no good node libraries for parsing gcov files. On the other hand, as of gcc14+, gcov (14+) can now output a report in json. But gcc 14 is the latest stable version of gcc, and it would be unfortunate to only support setups with the latest version of gcc.
You could also use python3 -m venv gcovr-venv
source grovr-venv/bin/activate
pip install gcovr
gcovr <search path where gcda/gcno files reside> --lcov lcov.info
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you! This works like a charm! One more thing, which might also relate to windows. When clicking on any file in the coverage browser, the following error message comes up: |
Beta Was this translation helpful? Give feedback.
-
|
Is the path correct? Does that file actually exist? Either way, I'm guessing you're correct that it could relate to the OS handling. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry guys, I was busy at work and then I missed/forgot about this. This is a bug that I'll fix in the extension. It turns out the lcov parser that we use returns a "carriage return" in the path when the lcov info file contains windows paths, which confuses vscode when we add coverage data that contains that path. I'll have a fix up imminently. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
No worries at all! Thanks for your contributions |
Beta Was this translation helpful? Give feedback.
I agree that this could have been nice. The problem with this approach is that there are no good node libraries for parsing gcov files. On the other hand, as of gcc14+, gcov (14+) can now output a report in json. But gcc 14 is the latest stable version of gcc, and it would be unfortunate to only support setups with the latest version of gcc.
You could also use
gcovr, a python pip module which can easily be installed and convert gcda/gcno files to an lcov report:python3 -m venv gcovr-venv source grovr-…