Bugzilla – Full Text Bug Listing
| Summary: | CommonBuilder should use EFSExtensionManager to determine build working directory | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Chris Recoskie <recoskie> | ||||||||||
| Component: | cdt-build | Assignee: | Chris Recoskie <recoskie> | ||||||||||
| Status: | RESOLVED FIXED | QA Contact: | Andrew Gvozdev <angvoz.dev> | ||||||||||
| Severity: | normal | ||||||||||||
| Priority: | P3 | CC: | cdt-build-inbox, cdtdoug, vivkong | ||||||||||
| Version: | 7.0.1 | ||||||||||||
| Target Milestone: | 7.0.2 | ||||||||||||
| Hardware: | All | ||||||||||||
| OS: | All | ||||||||||||
| Whiteboard: | |||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 181297 [details] proposed patch CommonBuilder currently has the following code in invokeMake(...): IPath workingDirectory = ManagedBuildManager.getBuildLocation(cfg, builder); URI workingDirectoryURI = ManagedBuildManager.getBuildLocationURI(cfg, builder); The workingDirectory is then passed to the command launcher when launching make. The workingDirectoryURI is currently only used for the error parser manager. Unforunately, this approach does not worked for linked EFS filesystems. The attached patch changes it so the workingDirectoryURI is used in conjunction with EFSExtensionManager to get a corresponding path. That path is then passed to the command launcher. I have tested this with both a remote, virtual EFS provider, and with a local CygWin project, and all seems fine. MBS Core tests all pass as well.