| Summary: | Not able to define relative include path using ".." (parent directory) with "workspace_loc" | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Yevgeny Shifrin <yevshif> |
| Component: | cdt-build | Assignee: | cdt-build-inbox <cdt-build-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Andrew Gvozdev <angvoz.dev> |
| Severity: | normal | ||
| Priority: | P3 | CC: | cdtdoug, remy.suen |
| Version: | 8.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 275779 | ||
Yevgeny, this is not Platform issue. In bug 353498 you requested to clarify description of the variable. *That* would be Platform issue. I will reclassify this bug. Hi, There are two issues that were obseved 353498 bug: 1) WorkspaceDirPath is no documented but works fine when using "..". 2) "workspace_loc" with ".." is not working. I am a bit confused which ticket should handle what :-) Thanks, Yevgeny I observe 3 issues there: 1) WorkspaceDirPath is not documented -> bug 353498 (see also its subj) 2) "workspace_loc" with ".." is not working -> this bug 3) The complain that ${workspace_loc} is not fully documented, specifically, it is not clear how to use arguments -> Platform folks would need to improve its description. I thought your focus was on that one. (In reply to comment #3) > I observe 3 issues there: > 1) WorkspaceDirPath is not documented -> bug 353498 (see also its subj) If you look at bug 353498, the original subject was: "Not able to define relative include path using ".." (parent directory)" Once I was able to use WorkspaceDirPath instead, I lowered the severity and changed the subject. In comment 3 you said: "But ${workspace_loc}/../dummy_include_path should also work which makes this report a bug." This is why according to my understanding issue 2) is not solved. > 2) "workspace_loc" with ".." is not working -> this bug 'this bug' pointed me to https://bugs.eclipse.org/bugs/show_bug.cgi?id=3 which does not seem to be related to our issue. > 3) The complain that ${workspace_loc} is not fully documented, specifically, it > is not clear how to use arguments -> Platform folks would need to improve its > description. I thought your focus was on that one. This is probably additional issue. Please let me know if I am missing something. Thanks, Yevgeny After looking a bit I understand my confusion with your previous answer. Editor by mistake created a hyperlink to bug number 3 :-) I agree with you that there are 3 issues as you described. * bug 353498 for issue "1" - CDT scope * this bug should handle issue "2" - Is it CDT or platform issue? * new bug is required for issue "3" - I can create a new bug for this. I am not sure what needs to be improved in the description. Thanks, Yevgeny (In reply to comment #5) > * this bug should handle issue "2" - Is it CDT or platform issue? This is CDT. CDT control interprets the expression as a whole. Fix coming for bug 416024 should resolve this issue. *** This bug has been marked as a duplicate of bug 416024 *** |
Build Identifier: 20110615-0604 Hi, I have the following file structure: 1) workspace location: /home/yevgenys/eclipse_workspaces/cdt8.0.0/temp2 2) directory location which I want to add as an include path: /home/yevgenys/eclipse_workspaces/cdt8.0.0/dummy_include_path I don't want to use absolute path. I defined it: ${workspace_loc}/../dummy_include_path After pressing ok, it was change to //../dummy_include_path and became "workspace path". If I use "WorkspaceDirPath" defined by CDT instead, it works. Please refer to https://bugs.eclipse.org/bugs/show_bug.cgi?id=353498 for more details. Thanks, Yevgeny Reproducible: Always