Colengms
commented
2 months ago Hi @jmailloux . Could set the setting: "C_Cpp.loggingLevel": "Debug" and provide the output of the C/C++ output channel leading up to the repro? That log should indicate the full command line used to query the compiler for system includes and defines, using the args from your configuration. Also, can you provide a specific example of something you are seeing that is not functioning as expected, so we can look at that specifically?
It looks like --param name=value should be handled properly by the extension and passed along to the compiler when the extension queries it for system includes and system defines. However, your usage of that var appears to be incorrect. The gcc command line arg docs indicate that an additional argument is expected to follow it. In your case --param is followed by -fno-rtti, which doesn't seem to be correct, so the --param and may be inadvertently preventing -fno-rtti from being used by the compiler. Perhaps this is a bug with how the Arduino extension generates configuration information?
Are you seeing a warning message about a failure to query the compiler? If not, the resulting configuration may be valid but incorrect, and due to incorrect args that the C/C++ extension is passing along to the compiler.
jmailloux
github-actions[bot]
Environment
Bug Summary and Steps to Reproduce
Bug Summary: A bunch of problems get flagged in C/C++ source files if there is "--param" in the "compilerArgs" list in c_cpp_properties.json. Removing "--param" fixes all of the problems. My c_cpp_properties was autogenerated by the Arduino extension.
Expected behavior: Having "--param" in the compilerArgs" list shouldn't be able to affect not identifying classes and things like that.
Configuration and Logs
Other Extensions
No response
Additional context
No response