Community
Participate
Working Groups
CDT 2.0.0.20045180809 There are three messages produced by Scanner Config: A. "Nonexistent include path [/some/big/imaginary/path]" B. "Unable to determine working directory for" C. "Ambiguous file path: ../test.cpp" (Text may change; see bug 63471) Some help is required to convey the reason and the impact of these messages to the user. Some suggested text: A: Something may be wrong with your build environment. The include has been added to the Removed list and will not be used to help the CDT parser's services. B: It appears you used a relative include path or paths in a build command whose working directory was difficult to deduce. Such path or paths may be missing from the list of Discovered Include Paths, which may hinder the CDT parser's services. You may wish to verify the Discovered Include Paths manually. You may resolve this message by letting make produce the working directory, or by specifying files unambiguously in the build command. C: hopefully same as B (see bug 63471 EXPECTED #2)
Vlad, you may need to provide some input to Dave Williams. Presently (CDT 2.0.0.200406140300), if I build CppTargetRTS I get about a thousand "error" messages (with the icon /!\) of the form: Ambiguous file path: ../src/RTAbortController/ct.cc The error message and icon is probably appropriate, but needs some explanation: where this message comes from and why, what its impact is, how to fix it, how to ignore it.
Not critical. Moving to 2.1.
I'm not even sure if this is relavant any more.
No, they are replaced with equally mysterious ones such as "Duplicate Path Entries" or "Invalid project path".
