You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2024. It is now read-only.
The arduino-cli has a CLI option --warnings string Optional, can be: none, default, more, all. Used to tell gcc which warning level to use (-W flag). (default "none") to set which warning compiler flags are used during compilation.
As a reminder, those are:
Can we either also expose this CLI option to the vscode-arduino plug-in (clean approach) or add a special case for compiler.warning_level when parsing buildPreferences to set
["--warnings", `${key}=${value}`]);
which is not so clean and rather a "temporary" solution 😇 .
What do you think?
The text was updated successfully, but these errors were encountered:
da-phil
changed the title
Feature request: adding option to set warning level
Feature request: adding arduino-cli option to set warning level (--warnings <level>)
Jun 4, 2024
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
See discussion #1508
The
arduino-cli
has a CLI option--warnings string Optional, can be: none, default, more, all. Used to tell gcc which warning level to use (-W flag). (default "none")
to set which warning compiler flags are used during compilation.As a reminder, those are:
In previous vscode-arduino versions somehow it was possible to set this option via
buildPreferences
:However this does not work anymore, as those are directly parsed to ``--build-property STRING` CLI options, see here:
vscode-arduino/src/arduino/arduino.ts
Line 151 in 6f24815
Can we either also expose this CLI option to the vscode-arduino plug-in (clean approach) or add a special case for
compiler.warning_level
when parsingbuildPreferences
to setwhich is not so clean and rather a "temporary" solution 😇 .
What do you think?
The text was updated successfully, but these errors were encountered: