Eclipse subfolders not inheriting project level includes
We have several Eclipse projects (using Eclipse build system). In most of the projects if I add some include path in project level settings (Project -> Properties -> C/C++ Build -> Settings -> ToolSettings -> Includes -> Include paths) they are visible when compiling all files within different subfolders of this project.
However, in one project it is not working - in some cases I have to set include paths seperately for each subfolder or even specific cpp files which are including headers from that path. Otherwise, during compilation included header is not visible to the compiler.
My initial suspiton was that it is caused by the way how folders are added to that project. It seemd to me that if folder type is "Linked Folder" (with Location set to PROJECT_LOC.. ...) then it is inherithing settings from project but if its type is "Folder" then it's not.
However, this probably is not the case beacuse after doing some changes (don't know what exact changes) that linked folder also started "to live on its own" (and also < folderInfo... structure appeared for that folder in .cproject file).
Therefore, another suspition is that if there are some changes done to folders/files then it's settings are branched out from project settings and it stops inherittings settings (or at least include paths).
Could someone explain what is the logic behind inheriting project level includes to subfolders/specific files? How to setup this correctly? And what is the best way to fix such situation where some folders are iheritting settings and some are not?
We are using:
Eclipse IDE for GNU ARM & RISC-V C/C++ Developers
Version: 2018-09 (4.9.0)
Build id: 20180930-0922
eclipse
asked Feb 15 at 15:58
QwerQwer
12
add a comment |
We have several Eclipse projects (using Eclipse build system). In most of the projects if I add some include path in project level settings (Project -> Properties -> C/C++ Build -> Settings -> ToolSettings -> Includes -> Include paths) they are visible when compiling all files within different subfolders of this project.
However, in one project it is not working - in some cases I have to set include paths seperately for each subfolder or even specific cpp files which are including headers from that path. Otherwise, during compilation included header is not visible to the compiler.
My initial suspiton was that it is caused by the way how folders are added to that project. It seemd to me that if folder type is "Linked Folder" (with Location set to PROJECT_LOC.. ...) then it is inherithing settings from project but if its type is "Folder" then it's not.
However, this probably is not the case beacuse after doing some changes (don't know what exact changes) that linked folder also started "to live on its own" (and also < folderInfo... structure appeared for that folder in .cproject file).
Therefore, another suspition is that if there are some changes done to folders/files then it's settings are branched out from project settings and it stops inherittings settings (or at least include paths).
Could someone explain what is the logic behind inheriting project level includes to subfolders/specific files? How to setup this correctly? And what is the best way to fix such situation where some folders are iheritting settings and some are not?
We are using:
Eclipse IDE for GNU ARM & RISC-V C/C++ Developers
Version: 2018-09 (4.9.0)
Build id: 20180930-0922
eclipse
asked Feb 15 at 15:58
QwerQwer
12
add a comment |
We have several Eclipse projects (using Eclipse build system). In most of the projects if I add some include path in project level settings (Project -> Properties -> C/C++ Build -> Settings -> ToolSettings -> Includes -> Include paths) they are visible when compiling all files within different subfolders of this project.
However, in one project it is not working - in some cases I have to set include paths seperately for each subfolder or even specific cpp files which are including headers from that path. Otherwise, during compilation included header is not visible to the compiler.
My initial suspiton was that it is caused by the way how folders are added to that project. It seemd to me that if folder type is "Linked Folder" (with Location set to PROJECT_LOC.. ...) then it is inherithing settings from project but if its type is "Folder" then it's not.
However, this probably is not the case beacuse after doing some changes (don't know what exact changes) that linked folder also started "to live on its own" (and also < folderInfo... structure appeared for that folder in .cproject file).
Therefore, another suspition is that if there are some changes done to folders/files then it's settings are branched out from project settings and it stops inherittings settings (or at least include paths).
Could someone explain what is the logic behind inheriting project level includes to subfolders/specific files? How to setup this correctly? And what is the best way to fix such situation where some folders are iheritting settings and some are not?
We are using:
Eclipse IDE for GNU ARM & RISC-V C/C++ Developers
Version: 2018-09 (4.9.0)
Build id: 20180930-0922
eclipse
asked Feb 15 at 15:58
QwerQwer
12
We have several Eclipse projects (using Eclipse build system). In most of the projects if I add some include path in project level settings (Project -> Properties -> C/C++ Build -> Settings -> ToolSettings -> Includes -> Include paths) they are visible when compiling all files within different subfolders of this project.
However, in one project it is not working - in some cases I have to set include paths seperately for each subfolder or even specific cpp files which are including headers from that path. Otherwise, during compilation included header is not visible to the compiler.
My initial suspiton was that it is caused by the way how folders are added to that project. It seemd to me that if folder type is "Linked Folder" (with Location set to PROJECT_LOC.. ...) then it is inherithing settings from project but if its type is "Folder" then it's not.
However, this probably is not the case beacuse after doing some changes (don't know what exact changes) that linked folder also started "to live on its own" (and also < folderInfo... structure appeared for that folder in .cproject file).
Therefore, another suspition is that if there are some changes done to folders/files then it's settings are branched out from project settings and it stops inherittings settings (or at least include paths).
Could someone explain what is the logic behind inheriting project level includes to subfolders/specific files? How to setup this correctly? And what is the best way to fix such situation where some folders are iheritting settings and some are not?
We are using:
Eclipse IDE for GNU ARM & RISC-V C/C++ Developers
Version: 2018-09 (4.9.0)
Build id: 20180930-0922
eclipse
eclipse
asked Feb 15 at 15:58
QwerQwer
12
asked Feb 15 at 15:58
QwerQwer
12
edited Feb 15 at 16:12
Qwer
asked Feb 15 at 15:58
QwerQwer
12
asked Feb 15 at 15:58
QwerQwer
12
asked Feb 15 at 15:58
QwerQwer
12
12
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1406152%2feclipse-subfolders-not-inheriting-project-level-includes%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 Super User!
- 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%2fsuperuser.com%2fquestions%2f1406152%2feclipse-subfolders-not-inheriting-project-level-includes%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
