| Summary: | [Scanner Discovery] [Parser] Features do not work on projects which are remotely compiled | ||
|---|---|---|---|
| Product: | [Tools] PTP | Reporter: | Guy <Guy.Milman> |
| Component: | RDT | Assignee: | Chris Recoskie <recoskie> |
| Status: | RESOLVED FIXED | QA Contact: | Greg Watson <g.watson> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | alan.escreet, cdtdoug, dave.daoust, victor.lenet |
| Version: | unspecified | ||
| Target Milestone: | 4.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Guy
Please provide an example that fails. Also, provide information regarding your build settings. Are you using managed or standard make? What compiler are you using? Does CDT discover the include paths for you? If you have some information that can help me identify and solve this problem, please feel free to reopen the defect. I provided every thing to John After discussion this is what Vladimir Hirsl [vhirsl@ca.ibm.com] had said: unfortunately, there is not much chance that Scanner Config discovered from the remote compilation is going to be useful. The reason is a step in Scanner Config discovery which tries to translate discovered include paths into absolute paths. Since discovered paths are on a different machine, the translation will fail since the paths are nonexistent on the local machine. The only way it could work is if both local and remote machines are *nix machines and the remote path is mounted on the same local path. But since your local machine is Windows, I am afraid it will not work. *** Bug 77180 has been marked as a duplicate of this bug. *** Future means you commit to fix it in the Future. Inboxes can't make committments. Moving to '--'. RDT has remote scanner discovery (although it's pretty glitchy right now). Given that the remote stuff is by and large living in RDT and not CDT, it makes sense to me to move this there. There has been remote scanner discovery for a long time now in RDT. |