diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-05 05:07:04 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-05 05:07:04 -0500 |
| commit | 84949b4b1d767b10e400bdb126d6091f0684cd65 (patch) | |
| tree | 89d1ab1f6d5899e345cb692f5382380389336c0e | |
| parent | f320da4632d014cfd576ce9ba7e65185d14f530a (diff) | |
| download | chime-84949b4b1d767b10e400bdb126d6091f0684cd65.tar.gz chime-84949b4b1d767b10e400bdb126d6091f0684cd65.zip | |
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.
| -rw-r--r-- | Makefile | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -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" |