vasm treat warnings as errors?

[hop]

Is there a way to make vasm return an exit code != 0 if it encounters a warning? The equivalent of /WX or -Werror C compiler options.

I've just discovered the very helpful -warncomm option, which catches a lot of errors in my code due to habitual use of spaces in expressions. I'd like the build to fail if warncomm fires.

vasmm68k_mot_x64.exe -kick1hunks -Fhunkexe -I..\NDK_3.9\Include\include_i -I..\include -o blitter-copy.exe -no-opt -warncomm blitter-copy.asm

vasm 1.8e (c) in 2002-2018 Volker Barthelmann
vasm M68k/CPU32/ColdFire cpu backend 2.3c (c) 2002-2018 Frank Wille
vasm motorola syntax module 3.12 (c) 2002-2018 Frank Wille
vasm hunk format output module 2.9c (c) 2002-2018 Frank Wille

warning 1019 in line 130 of "blitter-copy.asm": check comment
>PLAYFIELD_WIDTH_BYTES        EQU   PLAYFIELD_WIDTH_PIXELS / 8

code(acrx2):             900 bytes
bss(aurw1):               28 bytes
data_c(adrw2):           248 bytes
bss_c(aurw4):          86016 bytes

echo %errorlevel%
0

Note: I've modified the included NDK .i files, changing a load of * style comments to ; style to allow -warncomm to be used.

[phx]

Good idea. Done. Please check tomorrow's source snapshot.
The new option -wfail makes vasm return with an error code also on warnings.

[hop]

Excellent, thanks! And thanks for the great tool.

[hop]

Works a treat thanks.

vasm 1.8f (c) in 2002-2019 Volker Barthelmann
vasm M68k/CPU32/ColdFire cpu backend 2.3e (c) 2002-2019 Frank Wille
vasm motorola syntax module 3.12b (c) 2002-2019 Frank Wille
vasm hunk format output module 2.10 (c) 2002-2019 Frank Wille

warning 1019 in line 176 of "blitter-clear.asm": check comment
>PLAYFIELD_WIDTH_BYTES    EQU   PLAYFIELD_WIDTH_PIXELS / 8

code(acrx2):             866 bytes
bss(aurw1):               28 bytes
bss_c(aurw4):          86016 bytes

echo %errorlevel%
1