Closed Vladyyy closed 7 months ago
In the first: the implementation does treat the --base-directory
in a similar way to --source-directory
.
My bug is that I added it to the sourcedir list twice...and the second appearance is unused.
I believe that this is fixed in my sandbox - and will check in after some testing.
In the second invocation, the message
...unable to open~ gcda_gcno_data/tests.h ...
looks weird. Should not be a tilde character in the string.
I don't suppose you have a testcase that you can share.
Sorry, that's just me modifying the paths in the output above, what I wanted to demonstrate is that the --base-directory option is needed because otherwise lcov will complain it cannot find the sources
FWIW: we don't use the --base-directory
option - and instead use --source-directory
and --build-directory
.
The main reason is that the more complicated projects which need such a feature contain multiple components - and need a search path rather than a single location. YMMV.
We also end up using substitutions and a resolve callback - because the build layout doesn't always match the source layout (sometimes, in multiple repos).
The other observation is that your data is a bit unusual: 330K functions and 360K lines. If the numbers are right, then almost all of your code is one liners. Either you have very simple wrappers, or someone needs to start using newlines.
The other observation is that your data is a bit unusual: 330K functions and 360K lines.
Interesting, I'll take a closer look. Our logging macro instantiates a lambda so I suspect that's what's going on.
I think that this one is fixed as well - at least the proximate cause of the misleading message. An underlying issue may still remain. Could you try again (both command line versions) and report back? Please close if the issue seems fixed. Thanks Henry
Tested with TOT, I didn't hit the issue
Using the invocation below on TOT version fails with (this works with the latest release 2.0.1):
Omitting --base-directory option fails with: