The build happens in Docker, so we should run these tools inside Docker for simplicity. It would be useful to catch issues introduced when updating the code to be able to use newer versions of Poppler.
Manual steps to run clang-tidy:
- Copy the
clang_compilation_database.py from the Waf source to the root of this repository. link to master version 1
- In the Dockerfile, add
clang16-extra-tools to the list of Alpine packages to be installed.
- In the Dockerfile, add the
clang_compilation_database.py to the Dockerfile COPY.
- Build the image.
- Run a container from the image:
docker run -ti --entrypoint /bin/sh <IMAGE_ID>
$ cp ./build/compile_commands.json . && cd ..
$ clang-tidy -p compile_commands.json src/*.cpp src/*.h
TODO:
The build happens in Docker, so we should run these tools inside Docker for simplicity. It would be useful to catch issues introduced when updating the code to be able to use newer versions of Poppler.
Manual steps to run
clang-tidy:clang_compilation_database.pyfrom the Waf source to the root of this repository. link tomasterversion 1clang16-extra-toolsto the list of Alpine packages to be installed.clang_compilation_database.pyto the DockerfileCOPY.docker run -ti --entrypoint /bin/sh <IMAGE_ID>$ cp ./build/compile_commands.json . && cd ..$ clang-tidy -p compile_commands.json src/*.cpp src/*.hTODO:
syscall-reporter.cpp)clang-tidyflagsclang_compilation_databasetoolFootnotes
Version at time of writing in case the
masterlink breaks; ↩