From 84949b4b1d767b10e400bdb126d6091f0684cd65 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Tue, 5 May 2026 05:07:04 -0500 Subject: build: fail compile on byte-compile warnings I set `byte-compile-error-on-warn` to t in the root `compile' target. The warning backlog is clear, so any new warning should break the build instead of slipping by silently. --- Makefile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Makefile b/Makefile index 0f952b2..ca224e7 100644 --- a/Makefile +++ b/Makefile @@ -90,13 +90,13 @@ setup: # Byte-compile chime.el — surfaces free-variable / unused-let / suspicious-call # warnings that checkdoc and elisp-lint don't catch. byte-compile-error-on-warn -# stays nil for now to match `make build' permissiveness; tighten once the -# warning backlog is clear. +# is t so any warning fails the build; the backlog is clear and we want to keep +# it that way. compile: @echo "[i] Byte-compiling $(SOURCE_FILE)..." @$(EMACS_BATCH) \ --eval "(progn \ - (setq byte-compile-error-on-warn nil) \ + (setq byte-compile-error-on-warn t) \ (batch-byte-compile))" $(SOURCE_FILE) @echo "[✓] Compilation complete" -- cgit v1.2.3