Difference between revisions of "Using Visual Studio Code for ARM Development – Defines"
From EdWiki
(Created page with "__NOTOC__ == Using Visual Studio Code for ARM Development – Defines == center These errors are caused since the code I’m using, includi...") |
m (→Using Visual Studio Code for ARM Development – Defines) |
||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
== Using Visual Studio Code for ARM Development – Defines == | == Using Visual Studio Code for ARM Development – Defines == | ||
| − | [[image:vscode_defines_error.png|center]] | + | <!-- [[image:vscode_defines_error.png|center]] --> |
| − | + | It is common to pass defines to the compiler using flags at compile time. | |
| − | + | -D_DEBUG | |
| − | + | -DPART_TM4C123GH6PM | |
| − | - | + | |
| − | - | + | |
Setting these for VSCode is simple: just add them to the “defines” section of c_cpp_properties.json, without the -D flag prefix: | Setting these for VSCode is simple: just add them to the “defines” section of c_cpp_properties.json, without the -D flag prefix: | ||
| Line 14: | Line 12: | ||
<pre> | <pre> | ||
"defines": [ | "defines": [ | ||
| − | " | + | "DEBUG", |
| − | " | + | "PART_TM4C123GH6PM" |
], | ], | ||
</pre> | </pre> | ||
Revision as of 15:07, 21 March 2022
Using Visual Studio Code for ARM Development – Defines
It is common to pass defines to the compiler using flags at compile time.
-D_DEBUG -DPART_TM4C123GH6PM
Setting these for VSCode is simple: just add them to the “defines” section of c_cpp_properties.json, without the -D flag prefix:
"defines": [
"DEBUG",
"PART_TM4C123GH6PM"
],
This fixes all of the errors related to things defined in the libraries!
If the include paths and defines are properly set up in Visual Studio Code, the C/C++ plugin should be able to properly parse your code, identify syntax errors, and will provide Intellisense code completion to improve the speed and accuracy of your writing!