You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cloned the CodeChecker repository and later downloaded the CodeChecker 6.16.0 source ZIP. I ran into the same issue in both cases. I followed the installation instructions. After make package had finished, I tried this:
(CodeChecker venv) spielmann@robert-dev ~/devtools/codechecker-6.16.0 $ bin/CodeChecker
python3: can't open file '/home/spielmann/devtools/codechecker-6.16.0/lib/python3/codechecker_common/cli.py': [Errno 2] No such file or directory
I was obviously not smart enough to fully read the documentation, which does state that I should run build/CodeChecker/bin/CodeChecker, which works just fine. The trap I fell into was that, as a software engineer, I assumed that bin/CodeChecker would only materialize as the result of the build run. In fact it's there from the beginning.
Maybe it would make sense to point this out in the documentation for hasty people. This is just a cosmetic improvement suggestion. An alternative could be to move the file to a subdir with a different name, e.g. src.
The text was updated successfully, but these errors were encountered:
I cloned the CodeChecker repository and later downloaded the CodeChecker 6.16.0 source ZIP. I ran into the same issue in both cases. I followed the installation instructions. After
make package
had finished, I tried this:I was obviously not smart enough to fully read the documentation, which does state that I should run
build/CodeChecker/bin/CodeChecker
, which works just fine. The trap I fell into was that, as a software engineer, I assumed thatbin/CodeChecker
would only materialize as the result of the build run. In fact it's there from the beginning.Maybe it would make sense to point this out in the documentation for hasty people. This is just a cosmetic improvement suggestion. An alternative could be to move the file to a subdir with a different name, e.g.
src
.The text was updated successfully, but these errors were encountered: