feat: Create fake path for codechecker - #308
Conversation
nettle
left a comment
There was a problem hiding this comment.
I think we are just missing evidences here (use-case? tests?).
That's why this change does not look convincing to me so far.
Is it a part bigger change?
|
I'm not sure I understand your concerns. The main goal of this patch is to move away from using On the note of tests, since I'm only changing the environment codechecker runs in, any test running a codechecker analysis (e.g.: |
OK, it's getting clearer... Thanks for explanation! |
Why:
We want the Bazel rule to be as hermetic as possible.
What:
Addresses:
none
Notes:
Supporting standalone builds of CodeChecker, however, will still require Python in PATH.