Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Linux Tools Project/Remote Tools
Models
There are 2 remote models that Linux Tools intends to support.
- Local build, remote execution/profiling/debugging
- Remote build/execution/profiling/debug
The first model is one whereby the project builds locally but special profile launchers are added that allow the user to perform profiling on a compatible target. Compatibility includes platform, required libraries, and installed requirements. As one can guess, this can be difficult when the host and target machines are updated at different intervals. The remote profiling launch allows the user to specify a remote location to upload the executable to and perform profiling. The results of the profiling are shown in the local Eclipse session. At the moment, just Valgrind has support for this remote launching.
The second model does away with the compatibility requirement by keeping the source code on the remote target and building/executing there. The host Eclipse session can view the files and treats the project in all respects but location the same as a local project. The location of the project is set when the project is initially created. For a C/C++ project, the project wizards have a check-box for specifying a location other than in the current workspace. Once checked, remote file systems can also be specified via RSE (Remote System Explorer) connections. There is no special launcher for profiling tools needed as the regular settings are treated in terms of the remote location.