Michael Förderer
Michael Förderer
That's the problem. Use the MinGW toolchain to create coverage report.
You do not need to have the output files in a repo. Copy them back to the build directory and everything is fine. Please check https://gcc.gnu.org/onlinedocs/gcc/Freestanding-Environments.html.
No. Put the files back to the build folder and keep the rest as it is. The files contain the path names in the original structure.
It seems that you still using a different toolchain for report generation. `osal_gpio.gcno:version 'B32*', prefer '603*'`
You need to generate the report in your build PC or ensure to have the same version installed.
Stop mixing toolchains. Why installing something new in build PC? The toolchain which was used for the build is already there.
With every executable you can.
Pleas read the manual for the available formats. It's impossible to use the HTML report as Sonarqube XML. Why do you use different options for different formats (`--object-directory` is only...
Which error? All last errors where because of mixing different gcc toolchains. If you use the correct toolchain you need to check the verbose output why your data is filtered...
And according to the log we created the coverage data. Only one source file wasn't found by gcov.