Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PTP/designs/remote/cdt"
(→The Current Status) |
m (→Evaluation of CDT for EFS Support With an Emphasis on Remote File System) |
||
| Line 1: | Line 1: | ||
| − | = Evaluation of CDT for EFS Support With | + | = Evaluation of CDT for EFS Support With Emphasis on Remote File System = |
Our [[PTP/designs/remote|objective]] is to provide remote support for the Parallel Tools Project in a way that is natural to the user. The approach we take is to extend the new emerging Eclipse File System (EFS) with remote file system. As depending components, CDT/FDT needs to be modified to support EFS. | Our [[PTP/designs/remote|objective]] is to provide remote support for the Parallel Tools Project in a way that is natural to the user. The approach we take is to extend the new emerging Eclipse File System (EFS) with remote file system. As depending components, CDT/FDT needs to be modified to support EFS. | ||
Revision as of 03:02, 4 May 2006
Contents
Evaluation of CDT for EFS Support With Emphasis on Remote File System
Our objective is to provide remote support for the Parallel Tools Project in a way that is natural to the user. The approach we take is to extend the new emerging Eclipse File System (EFS) with remote file system. As depending components, CDT/FDT needs to be modified to support EFS.
The Current Status
CDT has no support for EFS at all. Even its support for locally linked resources, as a special example of EFS, are quite limited. For example, the standard make C projects does not support linked files. The following bugs are also identified:
- 136136 Build directory should not be restricted to workspace
- 70491 Invalid Include Path when "Link to Folder in the Filesystem"
And, also reference http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg03059.html for the discussion of linked resources.
What is Needed?
With EFS, projects or its component directories and files can be linked to different file systems, which can be local, remote, or virtual. The files and directories can be physically located at completely diverse places.
To support EFS while keeping the standard make builder, the CDT build has to be modified in the way that the files in the project can, when necessary, be replicated in a build directory (optionally on a remote build server) before the build command is invoked. The existing build directory of the C/C++ Build property can be exteded for this purpose and an additional property of build server can be added (see the picture).
The above process abstracts and covers many different cases. Some typical scenarios include, but not limited to:
- whole project on remote server: if the build machine is the same as the file server, then no replication is necessary; otherwise replicate.
- project with locally linked directories and files (linked to local file system): the files need to be replicated to a local build directory before invoking the build command.
- project with virtual file system (zip, for example): the files has to be replicated to a local build directory.
This will affect several other related components of CDT. Such components include the Indexer, Managed Make etc.
Roadmap to EFS Enablement for CDT
- Modify the code to allow build directory outside of workspace (fix to bug 136136)
- Modify CDT Project Creation/Conversion Wizard for EFS support
- Add build server property to the build property tab and modify the code to launch build command on build server
- Modify the affected components like Indexer and ManagedMake and fix those components [to be investigated]
- Enable file replication before build to support other scenarios