I am using Visual Studio Code in my C++ project. I installed Microsoft C/C++ Extension for VS Code. I got the following error:
#include errors detected. Please update your includePath. IntelliSense features for this translation unit (
/path/to/project/file.cpp
) will be provided by the Tag Parser.
asked Aug 9, 2017 at 6:50
3
Close and re-open Visual Studio Code.
answered Oct 13, 2018 at 19:38
Ivy GrowingIvy Growing
2,5582 gold badges17 silver badges23 bronze badges
3
The answer is here: How to use C/Cpp extension and add includepath to configurations.
Click the light bulb and then edit the JSON file which is opened. Choose the right block corresponding to your platform (there are Mac
, Linux
, Win32
– ms-vscode.cpptools version: 3). Update paths in includePath
(matters if you compile with VS Code) or browse.paths
(matters if you navigate with VS Code) or both.
Thanks to @Francesco Borzì, I will append his answer here:
You have to Left 🖰 click on the bulb next to the squiggled code line.
If a
#include
file or one of its dependencies cannot be found, you can also click on the red squiggles under the include statements to view suggestions for how to update your configuration.
answered Aug 9, 2017 at 6:51
banan3’14banan3’14
3,6983 gold badges24 silver badges46 bronze badges
8
If you are working with cmake-tools
and the error messages says something is wrong with the configurationProvider
, then you have 2 options:
- Use
ms-vscode.cpptools
instead ofms-vscode.cmake-tools
- Define the headers in
CMakeLists.txt
Option 1: Use ms-vscode.cpptools
instead of ms-vscode.cmake-tools
.
- Open c_cpp_properties.json. (windows key on windows or cmd key on mac + shift + p, enter «c/c++ edit configurations» and chose ‘json’.
- Enter ms-vscode.cpptools as value for configurationProvider instead of ms-vscode.cmake-tools or whatever you have.
How it should look like after the replacement of configurationProvider:
One other important configuration is the include path. The assumption is that you have this configuration right. May be like following
Option 2: Define the headers in CMakeLists.txt
When configurationProvider
is set to ms-vscode.cmake-tools
in c_cpp_properties.json
, VS Code uses the include information defined in the CMakeLists.txt
instead of reading the includePath
configs in VS Code.
So you need to setup the include path correctly:
- using the include_directories command (rather than the target_include_directories command) to define the headers
- Configure the project to reflect the change happened in the previous step.
mckelvin
3,8601 gold badge29 silver badges22 bronze badges
answered Jun 26, 2021 at 6:07
6
- Left mouse click on the bulb of error line
- Click
Edit Include path
- Then this window popup
- Just set
Compiler path
answered May 31, 2020 at 6:51
akashakash
7275 silver badges13 bronze badges
3
I ended up here after struggling for a while, but actually what I was missing was just:
If a #include file or one of its dependencies cannot be found, you can also click on the red squiggles under the include statements to view suggestions for how to update your configuration.
source: https://code.visualstudio.com/docs/languages/cpp#_intellisense
answered Jan 8, 2019 at 22:14
Francesco BorziFrancesco Borzi
55.1k46 gold badges176 silver badges250 bronze badges
2
The error message «Please update your includePath» does not necessarily mean there is actually a problem with the includePath
. The problem may be that VSCode is using the wrong compiler or wrong IntelliSense mode. I have written instructions in this answer on how to troubleshoot and align your VSCode C++ configuration with your compiler and project.
answered Aug 31, 2019 at 23:18
Scott McPeakScott McPeak
8,0462 gold badges39 silver badges72 bronze badges
0
I’m on a Macbook M1 Pro, and I had red squiggly error lines all over my C++ files. To solve, I did this:
- Open Preferences -> Settings
- Search for
intelliSenseEngine
- Change «C_Cpp: Intelli Sense Engine» from
Default
toTag Parser
alternatively, you could create a .vscode
folder in your project root, and then create a settings.json
with the content of
{
"C_Cpp.intelliSenseEngine" : "Tag Parser"
}
ideally, you should have a c_cpp_properties.json
file in the same folder with the right settings as well.
Note: I got this idea from Github here.
answered Oct 2, 2022 at 8:37
I was trying a hello world program, and this line:
#include <stdio.h>
was underlined green. I tried:
- Deleting the line
- Re-writing the line
- Clicking the yellow bulb and choosing to update
fixed the error warning. i don’t know if it fixed the actual problem. But then i’m compiling via a linux VM on Windows 10
answered Sep 20, 2017 at 12:14
Zach SmithZach Smith
8,34813 gold badges58 silver badges130 bronze badges
0
Go to your c_cpp_properties.json
file by searching from settings.There you might see the following code
{
"configurations": [
{
"name": "Linux",
"includePath": [
"${workspaceFolder}/**"
],
"defines": [],
"compilerPath": "/usr/bin/gcc",
"cStandard": "gnu17",
"cppStandard": "c++17",
"intelliSenseMode": "linux-gcc-x64"
}
],
"version": 4
}
Change the compiler path as below
"compilerPath": "/usr/bin/g++",
answered Mar 7, 2021 at 19:10
Sihat AfnanSihat Afnan
7227 silver badges14 bronze badges
1
An alternative answer would be opening VS Code in remote WSL, if you going to compile files with g++. Just close your VS Code and open WSL and type code .
After that the File Explorer shows that VS Code is now running in the context of WSL with the title bar [WSL: Ubuntu]. But make sure you’d installed the GNU compiler tools and the GDB debugger
on WSL.
source: https://code.visualstudio.com/docs/cpp/config-wsl
answered Jul 4, 2021 at 8:53
After closing and reopening VS, this should resolve.
answered Aug 9, 2019 at 20:59
PatrickPatrick
1191 silver badge3 bronze badges
- For Windows:
1.Install Mingw-w64
2.Then Edit environment variables for your account «C:mingw-w64x86_64-8.1.0-win32-seh-rt_v6-rev0mingw64bin»
3.Reload
-
For MAC
1.Open search ,command + shift +P, and run this code “c/c++ edit configurations (ui)”
2.open file c_cpp_properties.json and update the includePath from «${workspaceFolder}/**» to «${workspaceFolder}/inc»
answered Mar 18, 2020 at 14:31
If someone have this problem, maybe you just have to install build-essential.
apt install build-essential
answered May 21, 2020 at 0:27
PickiPicki
4594 silver badges11 bronze badges
For me, using Ubuntu, I just had to install gcc to solve this issue.
sudo apt install gcc
Then, set the compiler path to gcc. Go to your c_cpp_properties.json file, set:
"compilerPath": "/usr/bin/gcc"
answered Mar 8, 2021 at 20:17
after you install the c/c++ extension, two files are created inside .vscode folder.
open c_cpp_properties.json file and paste this key-value pair inside configuration object.(if it doesn’t already exists)
"configurationProvider": "ms-vscode-cpptools"
if it does already exists in the object, see if the value part is ms-vscode-cmaketools
. if such it is, replace that existing line with above line.
this will allow you to execute your cpp files along with c files.
answered Nov 2, 2022 at 13:42
I solved the error on my Mac by just clicking on the Edit «include path settings» and changing the compiler path to /usr/bin/clang
.
banan3’14
3,6983 gold badges24 silver badges46 bronze badges
answered Dec 2, 2022 at 17:29
In my case I did not need to close the whole VS-Code, closing the opened file (and sometimes even saving it) solved the issue.
answered Oct 21, 2020 at 8:17
My header file was in include/head.h
, code in src/code.cpp
. I wrote
#include "head.h"
and got this error. Changing it to
#include "../include/head.h"
fixed it.
answered Mar 16, 2022 at 22:06
Alex LiAlex Li
2374 silver badges11 bronze badges
2
I solved this problem, once I removed configurationProvider
node and set
cStandard
and cppStandard
to default values:
{
"configurations": [
{
"name": "Linux",
"includePath": [
"${workspaceFolder}",
"${workspaceFolder}/**",
"${workspaceFolder}/test",
"/opt/qt5/include/QtCore",
"${workspaceFolder}/test"
],
"defines": [],
"compilerPath": "/usr/bin/clang",
"cStandard": "${default}",
"cppStandard": "${default}",
"intelliSenseMode": "linux-clang-x64"
}
],
"version": 4
}
answered Aug 23, 2022 at 11:06
For Windows:
- Please add this directory to your environment variable(Path):
C:mingw-w64x86_64-8.1.0-win32-seh-rt_v6-rev0mingw64bin
- For Include errors detected, mention the path of your include folder into
«includePath»: [
«C:/mingw-w64/x86_64-8.1.0-win32-seh-rt_v6-rev0/mingw64/include/» ]
, as this is the path from where the compiler fetches the library to be included in your program.
answered Apr 4, 2020 at 8:30
In case you’ve copied and pasted code into your new file in VS Code
Please delete #include <iostream>
and try to build again.
banan3’14
3,6983 gold badges24 silver badges46 bronze badges
answered Dec 10, 2021 at 15:35
1
I am using Visual Studio Code in my C++ project. I installed Microsoft C/C++ Extension for VS Code. I got the following error:
#include errors detected. Please update your includePath. IntelliSense features for this translation unit (
/path/to/project/file.cpp
) will be provided by the Tag Parser.
asked Aug 9, 2017 at 6:50
3
Close and re-open Visual Studio Code.
answered Oct 13, 2018 at 19:38
Ivy GrowingIvy Growing
2,5582 gold badges17 silver badges23 bronze badges
3
The answer is here: How to use C/Cpp extension and add includepath to configurations.
Click the light bulb and then edit the JSON file which is opened. Choose the right block corresponding to your platform (there are Mac
, Linux
, Win32
– ms-vscode.cpptools version: 3). Update paths in includePath
(matters if you compile with VS Code) or browse.paths
(matters if you navigate with VS Code) or both.
Thanks to @Francesco Borzì, I will append his answer here:
You have to Left 🖰 click on the bulb next to the squiggled code line.
If a
#include
file or one of its dependencies cannot be found, you can also click on the red squiggles under the include statements to view suggestions for how to update your configuration.
answered Aug 9, 2017 at 6:51
banan3’14banan3’14
3,6983 gold badges24 silver badges46 bronze badges
8
If you are working with cmake-tools
and the error messages says something is wrong with the configurationProvider
, then you have 2 options:
- Use
ms-vscode.cpptools
instead ofms-vscode.cmake-tools
- Define the headers in
CMakeLists.txt
Option 1: Use ms-vscode.cpptools
instead of ms-vscode.cmake-tools
.
- Open c_cpp_properties.json. (windows key on windows or cmd key on mac + shift + p, enter «c/c++ edit configurations» and chose ‘json’.
- Enter ms-vscode.cpptools as value for configurationProvider instead of ms-vscode.cmake-tools or whatever you have.
How it should look like after the replacement of configurationProvider:
One other important configuration is the include path. The assumption is that you have this configuration right. May be like following
Option 2: Define the headers in CMakeLists.txt
When configurationProvider
is set to ms-vscode.cmake-tools
in c_cpp_properties.json
, VS Code uses the include information defined in the CMakeLists.txt
instead of reading the includePath
configs in VS Code.
So you need to setup the include path correctly:
- using the include_directories command (rather than the target_include_directories command) to define the headers
- Configure the project to reflect the change happened in the previous step.
mckelvin
3,8601 gold badge29 silver badges22 bronze badges
answered Jun 26, 2021 at 6:07
6
- Left mouse click on the bulb of error line
- Click
Edit Include path
- Then this window popup
- Just set
Compiler path
answered May 31, 2020 at 6:51
akashakash
7275 silver badges13 bronze badges
3
I ended up here after struggling for a while, but actually what I was missing was just:
If a #include file or one of its dependencies cannot be found, you can also click on the red squiggles under the include statements to view suggestions for how to update your configuration.
source: https://code.visualstudio.com/docs/languages/cpp#_intellisense
answered Jan 8, 2019 at 22:14
Francesco BorziFrancesco Borzi
55.1k46 gold badges176 silver badges250 bronze badges
2
The error message «Please update your includePath» does not necessarily mean there is actually a problem with the includePath
. The problem may be that VSCode is using the wrong compiler or wrong IntelliSense mode. I have written instructions in this answer on how to troubleshoot and align your VSCode C++ configuration with your compiler and project.
answered Aug 31, 2019 at 23:18
Scott McPeakScott McPeak
8,0462 gold badges39 silver badges72 bronze badges
0
I’m on a Macbook M1 Pro, and I had red squiggly error lines all over my C++ files. To solve, I did this:
- Open Preferences -> Settings
- Search for
intelliSenseEngine
- Change «C_Cpp: Intelli Sense Engine» from
Default
toTag Parser
alternatively, you could create a .vscode
folder in your project root, and then create a settings.json
with the content of
{
"C_Cpp.intelliSenseEngine" : "Tag Parser"
}
ideally, you should have a c_cpp_properties.json
file in the same folder with the right settings as well.
Note: I got this idea from Github here.
answered Oct 2, 2022 at 8:37
I was trying a hello world program, and this line:
#include <stdio.h>
was underlined green. I tried:
- Deleting the line
- Re-writing the line
- Clicking the yellow bulb and choosing to update
fixed the error warning. i don’t know if it fixed the actual problem. But then i’m compiling via a linux VM on Windows 10
answered Sep 20, 2017 at 12:14
Zach SmithZach Smith
8,34813 gold badges58 silver badges130 bronze badges
0
Go to your c_cpp_properties.json
file by searching from settings.There you might see the following code
{
"configurations": [
{
"name": "Linux",
"includePath": [
"${workspaceFolder}/**"
],
"defines": [],
"compilerPath": "/usr/bin/gcc",
"cStandard": "gnu17",
"cppStandard": "c++17",
"intelliSenseMode": "linux-gcc-x64"
}
],
"version": 4
}
Change the compiler path as below
"compilerPath": "/usr/bin/g++",
answered Mar 7, 2021 at 19:10
Sihat AfnanSihat Afnan
7227 silver badges14 bronze badges
1
An alternative answer would be opening VS Code in remote WSL, if you going to compile files with g++. Just close your VS Code and open WSL and type code .
After that the File Explorer shows that VS Code is now running in the context of WSL with the title bar [WSL: Ubuntu]. But make sure you’d installed the GNU compiler tools and the GDB debugger
on WSL.
source: https://code.visualstudio.com/docs/cpp/config-wsl
answered Jul 4, 2021 at 8:53
After closing and reopening VS, this should resolve.
answered Aug 9, 2019 at 20:59
PatrickPatrick
1191 silver badge3 bronze badges
- For Windows:
1.Install Mingw-w64
2.Then Edit environment variables for your account «C:mingw-w64x86_64-8.1.0-win32-seh-rt_v6-rev0mingw64bin»
3.Reload
-
For MAC
1.Open search ,command + shift +P, and run this code “c/c++ edit configurations (ui)”
2.open file c_cpp_properties.json and update the includePath from «${workspaceFolder}/**» to «${workspaceFolder}/inc»
answered Mar 18, 2020 at 14:31
If someone have this problem, maybe you just have to install build-essential.
apt install build-essential
answered May 21, 2020 at 0:27
PickiPicki
4594 silver badges11 bronze badges
For me, using Ubuntu, I just had to install gcc to solve this issue.
sudo apt install gcc
Then, set the compiler path to gcc. Go to your c_cpp_properties.json file, set:
"compilerPath": "/usr/bin/gcc"
answered Mar 8, 2021 at 20:17
after you install the c/c++ extension, two files are created inside .vscode folder.
open c_cpp_properties.json file and paste this key-value pair inside configuration object.(if it doesn’t already exists)
"configurationProvider": "ms-vscode-cpptools"
if it does already exists in the object, see if the value part is ms-vscode-cmaketools
. if such it is, replace that existing line with above line.
this will allow you to execute your cpp files along with c files.
answered Nov 2, 2022 at 13:42
I solved the error on my Mac by just clicking on the Edit «include path settings» and changing the compiler path to /usr/bin/clang
.
banan3’14
3,6983 gold badges24 silver badges46 bronze badges
answered Dec 2, 2022 at 17:29
In my case I did not need to close the whole VS-Code, closing the opened file (and sometimes even saving it) solved the issue.
answered Oct 21, 2020 at 8:17
My header file was in include/head.h
, code in src/code.cpp
. I wrote
#include "head.h"
and got this error. Changing it to
#include "../include/head.h"
fixed it.
answered Mar 16, 2022 at 22:06
Alex LiAlex Li
2374 silver badges11 bronze badges
2
I solved this problem, once I removed configurationProvider
node and set
cStandard
and cppStandard
to default values:
{
"configurations": [
{
"name": "Linux",
"includePath": [
"${workspaceFolder}",
"${workspaceFolder}/**",
"${workspaceFolder}/test",
"/opt/qt5/include/QtCore",
"${workspaceFolder}/test"
],
"defines": [],
"compilerPath": "/usr/bin/clang",
"cStandard": "${default}",
"cppStandard": "${default}",
"intelliSenseMode": "linux-clang-x64"
}
],
"version": 4
}
answered Aug 23, 2022 at 11:06
For Windows:
- Please add this directory to your environment variable(Path):
C:mingw-w64x86_64-8.1.0-win32-seh-rt_v6-rev0mingw64bin
- For Include errors detected, mention the path of your include folder into
«includePath»: [
«C:/mingw-w64/x86_64-8.1.0-win32-seh-rt_v6-rev0/mingw64/include/» ]
, as this is the path from where the compiler fetches the library to be included in your program.
answered Apr 4, 2020 at 8:30
In case you’ve copied and pasted code into your new file in VS Code
Please delete #include <iostream>
and try to build again.
banan3’14
3,6983 gold badges24 silver badges46 bronze badges
answered Dec 10, 2021 at 15:35
1
If you got this problem, Relax, u r probablu 1000th one here
I have added screenshots, these are not links to some terrifying third party documentations (;
Solution
1.installation of c++ :
check you have the c++ installed, (it dosent come pre-installed! You have to do it)
If not install it. If you have installed it, navigate to it, and get the path
click on the path at top in file explorer, and Ctrl+C to copy it here is how u get the path
2.path environment variable setup
steps:
i.left click This pc(in file explorer)here
ii. manage this menu will open
iii. scroll down in the about section, find «Advanced System Settings» and follow along this
V. «edit environment variable» dialogue box will open, click new, then paste the link to the gcc compiler that you installed firstly.
Now, this path is set as environment variable, try running command : gcc —version in command panel, if still there is error, try uploading different paths of gcc.exe to the environment variable «Path». Also, re-starting pc is recommended if path variable change doesn’t appear.
Now we start(or restart if it was open) the Vs-code(just a little to go)
i. Shift+Ctrl+p then : follow this
ii.then this
if the dropdown dosnt show any option, try re-starting vs-code, or pc, re-setting the environment variable step, or re-installing c++ and starting over(in worst case)
iii.scroll down the same page, and paste the path to include folders from c++ to text box corrosponding to «Include path» . you have to first get this path, search for folder with name «include», copy and add its path.(many times, ide is capable to automate this step;))
Now try running the code, it must be good to go, but iff it still throws error, try repeating process of adding environment variable, re-staqrting vscode, or even then, re-installing c++.
@michelleangela
Log diagnostics without error (file not open):
——— Diagnostics — 10.12.2019, 21:23:48
Version: 0.26.2
Current Configuration:
{
«name»: «Win32»,
«includePath»: [
«c:/OneDrive/Projekte/PlatformIO/Projects/Display XPT2046/include»,
«c:/OneDrive/Projekte/PlatformIO/Projects/Display XPT2046/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/SPI/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/cores/arduino»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/variants/eightanaloginputs»,
«C:/Users/wapjoe/.platformio/lib/Adafruit FRAM I2C_ID658»,
«C:/Users/wapjoe/.platformio/lib/DHTlib_ID1336»,
«C:/Users/wapjoe/.platformio/lib/RunningMedian_ID1361»,
«C:/Users/wapjoe/.platformio/lib/SFFS_ID2037»,
«C:/Users/wapjoe/.platformio/lib/Ticker_ID1586»,
«C:/Users/wapjoe/.platformio/lib/Time_ID44»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/EEPROM/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/HID/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/SoftwareSerial/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/Wire/src»,
«C:/Users/wapjoe/.platformio/packages/tool-unity»
],
«browse»: {
«limitSymbolsToIncludedHeaders»: true,
«path»: [
«c:/OneDrive/Projekte/PlatformIO/Projects/Display XPT2046/include»,
«c:/OneDrive/Projekte/PlatformIO/Projects/Display XPT2046/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/SPI/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/cores/arduino»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/variants/eightanaloginputs»,
«C:/Users/wapjoe/.platformio/lib/Adafruit FRAM I2C_ID658»,
«C:/Users/wapjoe/.platformio/lib/DHTlib_ID1336»,
«C:/Users/wapjoe/.platformio/lib/RunningMedian_ID1361»,
«C:/Users/wapjoe/.platformio/lib/SFFS_ID2037»,
«C:/Users/wapjoe/.platformio/lib/Ticker_ID1586»,
«C:/Users/wapjoe/.platformio/lib/Time_ID44»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/EEPROM/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/HID/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/SoftwareSerial/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/Wire/src»,
«C:/Users/wapjoe/.platformio/packages/tool-unity»
]
},
«defines»: [
«PLATFORMIO=40100»,
«ARDUINO_AVR_NANO»,
«F_CPU=16000000L»,
«ARDUINO_ARCH_AVR»,
«ARDUINO=10808»,
«AVR_ATmega328P«
],
«intelliSenseMode»: «clang-x64»,
«cStandard»: «c11»,
«cppStandard»: «c++11»,
«compilerPath»: «C:/Users/wapjoe/.platformio/packages/toolchain-atmelavr/bin/avr-gcc.exe»,
«compilerArgs»: [
«-mmcu=atmega328p»
]
}
No active translation units.
Log diagnosis with error (file opened):
——— Diagnostics — 10.12.2019, 21:25:23
Version: 0.26.2
Current Configuration:
{
«name»: «Win32»,
«includePath»: [
«c:/OneDrive/Projekte/PlatformIO/Projects/Ergometer ProMini 1.0/include»,
«c:/OneDrive/Projekte/PlatformIO/Projects/Ergometer ProMini 1.0/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/Wire/src»,
«C:/Users/wapjoe/.platformio/lib/Ticker_ID1586»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/SoftwareSerial/src»,
«C:/Users/wapjoe/.platformio/lib/RunningMedian_ID1361»,
«C:/Users/wapjoe/.platformio/lib/DHTlib_ID1336»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/cores/arduino»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/variants/eightanaloginputs»,
«C:/Users/wapjoe/.platformio/lib/Adafruit FRAM I2C_ID658»,
«C:/Users/wapjoe/.platformio/lib/SFFS_ID2037»,
«C:/Users/wapjoe/.platformio/lib/Time_ID44»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/EEPROM/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/HID/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/SPI/src»,
«C:/Users/wapjoe/.platformio/packages/tool-unity»
],
«browse»: {
«limitSymbolsToIncludedHeaders»: true,
«path»: [
«c:/OneDrive/Projekte/PlatformIO/Projects/Ergometer ProMini 1.0/include»,
«c:/OneDrive/Projekte/PlatformIO/Projects/Ergometer ProMini 1.0/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/Wire/src»,
«C:/Users/wapjoe/.platformio/lib/Ticker_ID1586»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/SoftwareSerial/src»,
«C:/Users/wapjoe/.platformio/lib/RunningMedian_ID1361»,
«C:/Users/wapjoe/.platformio/lib/DHTlib_ID1336»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/cores/arduino»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/variants/eightanaloginputs»,
«C:/Users/wapjoe/.platformio/lib/Adafruit FRAM I2C_ID658»,
«C:/Users/wapjoe/.platformio/lib/SFFS_ID2037»,
«C:/Users/wapjoe/.platformio/lib/Time_ID44»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/EEPROM/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/HID/src»,
«C:/Users/wapjoe/.platformio/packages/framework-arduino-avr/libraries/SPI/src»,
«C:/Users/wapjoe/.platformio/packages/tool-unity»
]
},
«defines»: [
«PLATFORMIO=40100»,
«ARDUINO_AVR_PRO»,
«F_CPU=16000000L»,
«ARDUINO_ARCH_AVR»,
«ARDUINO=10808»,
«AVR_ATmega328P«
],
«intelliSenseMode»: «clang-x64»,
«cStandard»: «c11»,
«cppStandard»: «c++11»,
«compilerPath»: «C:/Users/wapjoe/.platformio/packages/toolchain-atmelavr/bin/avr-gcc.exe»,
«compilerArgs»: [
«-mmcu=atmega328p»
]
}
Translation Unit Mappings:
[ C:OneDriveProjektePlatformIOProjectsErgometer ProMini 1.0srcmain.cpp ]:
C:ONEDRIVEPROJEKTEPLATFORMIOPROJECTSERGOMETER PROMINI 1.0SRCMAIN.CPP
Translation Unit Configurations:
[ C:OneDriveProjektePlatformIOProjectsErgometer ProMini 1.0srcmain.cpp ]:
Process ID: 19720
Memory Usage: 19 MB
Compiler Path: C:/Users/wapjoe/.platformio/packages/toolchain-atmelavr/bin/avr-gcc.exe
Includes:
C:ONEDRIVEPROJEKTEPLATFORMIOPROJECTSERGOMETER PROMINI 1.0INCLUDE
C:ONEDRIVEPROJEKTEPLATFORMIOPROJECTSERGOMETER PROMINI 1.0SRC
C:USERSWAPJOE.PLATFORMIOPACKAGESFRAMEWORK-ARDUINO-AVRLIBRARIESWIRESRC
C:USERSWAPJOE.PLATFORMIOLIBTICKER_ID1586
C:USERSWAPJOE.PLATFORMIOPACKAGESFRAMEWORK-ARDUINO-AVRLIBRARIESSOFTWARESERIALSRC
C:USERSWAPJOE.PLATFORMIOLIBRUNNINGMEDIAN_ID1361
C:USERSWAPJOE.PLATFORMIOLIBDHTLIB_ID1336
C:USERSWAPJOE.PLATFORMIOPACKAGESFRAMEWORK-ARDUINO-AVRCORESARDUINO
C:USERSWAPJOE.PLATFORMIOPACKAGESFRAMEWORK-ARDUINO-AVRVARIANTSEIGHTANALOGINPUTS
C:USERSWAPJOE.PLATFORMIOLIBADAFRUIT FRAM I2C_ID658
C:USERSWAPJOE.PLATFORMIOLIBSFFS_ID2037
C:USERSWAPJOE.PLATFORMIOLIBTIME_ID44
C:USERSWAPJOE.PLATFORMIOPACKAGESFRAMEWORK-ARDUINO-AVRLIBRARIESEEPROMSRC
C:USERSWAPJOE.PLATFORMIOPACKAGESFRAMEWORK-ARDUINO-AVRLIBRARIESHIDSRC
C:USERSWAPJOE.PLATFORMIOPACKAGESFRAMEWORK-ARDUINO-AVRLIBRARIESSPISRC
C:USERSWAPJOE.PLATFORMIOPACKAGESTOOL-UNITY
C:USERSWAPJOE.PLATFORMIOPACKAGESTOOLCHAIN-ATMELAVRLIBGCCAVR5.4.0INCLUDE
C:USERSWAPJOE.PLATFORMIOPACKAGESTOOLCHAIN-ATMELAVRLIBGCCAVR5.4.0INCLUDE-FIXED
C:USERSWAPJOE.PLATFORMIOPACKAGESTOOLCHAIN-ATMELAVRAVRINCLUDE
Defines:
PLATFORMIO=40100
ARDUINO_AVR_PRO
F_CPU=16000000L
ARDUINO_ARCH_AVR
ARDUINO=10808
AVR_ATmega328P
Standard Version: c++11
IntelliSense Mode: gcc-x64
Other Flags:
—g++
—gnu_version=50400
Total Memory Usage: 19 MB
Loading