6 Commits

Include renames

Author	SHA1	Message	Date
AramJonghu	b3c72bd476	chore(Dockerfile): add future dependencies	2026-10-25 01:34:38 +02:00
AramJonghu	8cc9ff36e7	ci: rework Dockerfile image + buildx dep added	2026-10-25 01:34:38 +02:00
AramJonghu	417be33c6a	fix(ci): missing dependency wayland-scanner	2026-10-25 01:34:38 +02:00
AramJonghuandzach	5ec682d780	fix(Docker): add required deps to dockerfile	2026-09-30 15:01:19 +02:00
AramJonghu	abf7382771	ci: libcava dev headers	2026-08-14 20:00:27 +02:00
AramJonghuandzach	bc9d8af0fe	update to clang-tidy + workflow improvement cpp build & lint check (#130) ... ### Goal Idea is to reduce the annoyances and research which clang-tidy rules make sense and actually have benefits in our project. Also considering immediately resolving most if not all tidy warnings. ### Current Changes - `.clang-tidy` has changes to follow the guidelines we have been following silently. Some rules were different from how we program. - Note that naming is completely removed and won't be checked. In a future PR (where we go over the code to fix linting issues), we can reintroduce them and make sure they fit our codebase consistently. - tidy rules are not considered errors anymore (stopped compile). - CI/CD addition to build check and clang-tidy check. Tried to get clang-tidy check to show when failed, but that causes complications in its checks; so now it is simply silent when failing. - Dockerfile that creates an arch container as cache for the CI/CD, prevents redownload of dependencies each run. Instead, it runs weekly (or optionally a different interval). ### Current complications - To push the docker container build, it would require this webserver to allow larger filesize pushes (need ~2GB). Current workaround is arguably better where docker build is pushed to runner server. - Figuring out which clang-tidy rules make sense. Reviewed-on: #130 Co-authored-by: AramJonghu <aramjonghu@tutamail.com> Co-committed-by: AramJonghu <aramjonghu@tutamail.com>	2026-06-29 22:10:26 +02:00