With Nim 1.6.8, the warnings appear no matter whether --cpu:arm is passed on the command line or not. I assume this is a fix to harmonize behavior between config and command line flags.
I asked Araq on Discord, and the incompatible pointer type warnings are expected and not an issue.
Nim itself, when it invokes gcc, always passes the -w flag which suppresses all warnings.
Therefore, I propose to imitate the Nim compiler behavior and pass -w to gcc for all Nim-generated C files. This is implemented via a set_source_file_properties in the CMake file and only affects the Nim-generated sources, not the other (pico SDK, external libs, etc) C source files.
Yes, I could have lived with warnings, but I like my terminal output clean and pretty looking 🙃.
Resolves #55
With Nim 1.6.8, the warnings appear no matter whether
--cpu:armis passed on the command line or not. I assume this is a fix to harmonize behavior between config and command line flags.I asked Araq on Discord, and the incompatible pointer type warnings are expected and not an issue.
Nim itself, when it invokes gcc, always passes the
-wflag which suppresses all warnings.Therefore, I propose to imitate the Nim compiler behavior and pass
-wto gcc for all Nim-generated C files. This is implemented via aset_source_file_propertiesin the CMake file and only affects the Nim-generated sources, not the other (pico SDK, external libs, etc) C source files.Yes, I could have lived with warnings, but I like my terminal output clean and pretty looking 🙃.