C include paths in VS Code - where from?
I am putting together a simple C project in VS Code which would just compile a single C file using GCC compiler.
I have created a c_cpp_properties.json and tasks.json.
It is unclear to me where is the GCC compiler supposed to get include directories from.
When include dirs are added to c_cpp_properties.json via the includePath
"configurations": [
{
"name": "Win32",
"includePath": [
"C:/include/path1",
"C:/include/path2"
],...
it doesn't work.
It only compiles successfully when I add the paths as compiler arguments to tasks.json:
"tasks":
[
{
"label": "Compile C file",
"type": "shell",
"command": "gcc",
"args": [
"-g",
"-I",
"C:/include/path1",
"-c",
"myfile.c"
],...
Where is the GCC compiler supposed to get include directories from?
What is the includePath in c_cpp_properties.json for?
c_cpp_properties.json Reference Guide says:
- includePath:
If "C_Cpp.intelliSenseEngine" is set to "Default" in your settings file, this list of paths will be used by IntelliSense to search for headers included by your source files. This is basically the same as the list of paths you pass to your compiler with the -I switch. If a path ends with /** the IntelliSense engine will do a recursive search for includes starting from that directory. If on Windows with Visual Studio installed, or if a compiler is specified in the compilerPath setting, it is not necessary to list the system include paths in this list.
visual-studio-code
asked Nov 23 '18 at 10:10
DanijelDanijel
2,553124886
add a comment |
I am putting together a simple C project in VS Code which would just compile a single C file using GCC compiler.
I have created a c_cpp_properties.json and tasks.json.
It is unclear to me where is the GCC compiler supposed to get include directories from.
When include dirs are added to c_cpp_properties.json via the includePath
"configurations": [
{
"name": "Win32",
"includePath": [
"C:/include/path1",
"C:/include/path2"
],...
it doesn't work.
It only compiles successfully when I add the paths as compiler arguments to tasks.json:
"tasks":
[
{
"label": "Compile C file",
"type": "shell",
"command": "gcc",
"args": [
"-g",
"-I",
"C:/include/path1",
"-c",
"myfile.c"
],...
Where is the GCC compiler supposed to get include directories from?
What is the includePath in c_cpp_properties.json for?
c_cpp_properties.json Reference Guide says:
- includePath:
If "C_Cpp.intelliSenseEngine" is set to "Default" in your settings file, this list of paths will be used by IntelliSense to search for headers included by your source files. This is basically the same as the list of paths you pass to your compiler with the -I switch. If a path ends with /** the IntelliSense engine will do a recursive search for includes starting from that directory. If on Windows with Visual Studio installed, or if a compiler is specified in the compilerPath setting, it is not necessary to list the system include paths in this list.
visual-studio-code
asked Nov 23 '18 at 10:10
DanijelDanijel
2,553124886
add a comment |
I am putting together a simple C project in VS Code which would just compile a single C file using GCC compiler.
I have created a c_cpp_properties.json and tasks.json.
It is unclear to me where is the GCC compiler supposed to get include directories from.
When include dirs are added to c_cpp_properties.json via the includePath
"configurations": [
{
"name": "Win32",
"includePath": [
"C:/include/path1",
"C:/include/path2"
],...
it doesn't work.
It only compiles successfully when I add the paths as compiler arguments to tasks.json:
"tasks":
[
{
"label": "Compile C file",
"type": "shell",
"command": "gcc",
"args": [
"-g",
"-I",
"C:/include/path1",
"-c",
"myfile.c"
],...
Where is the GCC compiler supposed to get include directories from?
What is the includePath in c_cpp_properties.json for?
c_cpp_properties.json Reference Guide says:
- includePath:
If "C_Cpp.intelliSenseEngine" is set to "Default" in your settings file, this list of paths will be used by IntelliSense to search for headers included by your source files. This is basically the same as the list of paths you pass to your compiler with the -I switch. If a path ends with /** the IntelliSense engine will do a recursive search for includes starting from that directory. If on Windows with Visual Studio installed, or if a compiler is specified in the compilerPath setting, it is not necessary to list the system include paths in this list.
visual-studio-code
asked Nov 23 '18 at 10:10
DanijelDanijel
2,553124886
I am putting together a simple C project in VS Code which would just compile a single C file using GCC compiler.
I have created a c_cpp_properties.json and tasks.json.
It is unclear to me where is the GCC compiler supposed to get include directories from.
When include dirs are added to c_cpp_properties.json via the includePath
"configurations": [
{
"name": "Win32",
"includePath": [
"C:/include/path1",
"C:/include/path2"
],...
it doesn't work.
It only compiles successfully when I add the paths as compiler arguments to tasks.json:
"tasks":
[
{
"label": "Compile C file",
"type": "shell",
"command": "gcc",
"args": [
"-g",
"-I",
"C:/include/path1",
"-c",
"myfile.c"
],...
Where is the GCC compiler supposed to get include directories from?
What is the includePath in c_cpp_properties.json for?
c_cpp_properties.json Reference Guide says:
- includePath:
If "C_Cpp.intelliSenseEngine" is set to "Default" in your settings file, this list of paths will be used by IntelliSense to search for headers included by your source files. This is basically the same as the list of paths you pass to your compiler with the -I switch. If a path ends with /** the IntelliSense engine will do a recursive search for includes starting from that directory. If on Windows with Visual Studio installed, or if a compiler is specified in the compilerPath setting, it is not necessary to list the system include paths in this list.
visual-studio-code
visual-studio-code
asked Nov 23 '18 at 10:10
DanijelDanijel
2,553124886
asked Nov 23 '18 at 10:10
DanijelDanijel
2,553124886
edited Nov 23 '18 at 10:35
Danijel
asked Nov 23 '18 at 10:10
DanijelDanijel
2,553124886
asked Nov 23 '18 at 10:10
DanijelDanijel
2,553124886
asked Nov 23 '18 at 10:10
DanijelDanijel
2,553124886
2,553124886
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53444644%2fc-include-paths-in-vs-code-where-from%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53444644%2fc-include-paths-in-vs-code-where-from%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
