| Feature Request: Individual project Launch configuration file [message #1869315] |
Mon, 12 August 2024 04:54  |
Eclipse User |
|
|
|
Preface:
This is a proposal to ease the use of Run/Debug launch configurations for complex projects.
Note: This has not been proof-checked with the latest stand-alone Eclipse, but based on my usage of several IDE's for embedded microcontrollers all based on Eclipse, such as Renesas E2Studio.
Background:
On complex embedded hardware, multiple microcontrollers are typically in use. Each of these are developed as independent projects with their own repositories. Each of them also uses multiple run/debug launch profiles, often with a lot of complex configuration for multiple targets, such as simulation, HiL and real hardware. 8-10 launch configurations per project are quite normal.
Current behaviour:
Run/Launch configurations from all currently open projects in a workspace are saved globally to one file, which can be placed one of two places:
- As a local file in the current workspace.
- As a "shared file", where all open projects use the same shared file somewhere in the filesystem.
Similar, run/debug configurations are loaded from those two locations for all projects.
Problem with the current run/debug launch configuration system:
- Launch configurations are complex to set up, and is in essence to be seen as source code. Yet it's not possible to easily ensure that the launch configuration for a specific project is saved next to the projects .project file.
- It's hard to share launch configurations for a single project.
- It's hard to commit launch configurations to a repository.
- In order to save launch configurations to a project folder, one need to use the export option, then manually select the, say 10 launch configurations out of 60, browse to the project in the filesystem, and save the file. This is very error prone.
- In order to import the exported launch configurations files, one first need to browse to the filesystem, then import. Import always imports everything, which means that if a single configuration has been added, but 9 remain the same, then after import you will have the new configuration, and 9 duplicated configurations with an added [x] counter, that you manually need to clean up.
Proposal
- Always save the run/debug launch configuration file for a given project next the the .project file in said project.
- Maintain the current options, but dynamically populate the global file from the launch files found in the projects that are currently opened in the current workspace.
Benefits
- Traceability: Debug/Run configurations belongs to a project, and can be committed together with the rest of the project code.
- Reduce clutter: Multiple projects can be in a workspace, and only the launch configurations for the open projects are actually shown in the list.
- Flexibility: If I add a new project to my workspace, I don't have to manually import the new projects launch configurations.
- Flexibility: If I close or remove a project from my workspace, I don't have to manually remove the unused launch configurations.
Postscript
I can't believe somebody didn't already think about this - but I couldn't find anything to suggest it's been proposed before.
Why isn't it already like this?
Are the plugins that changes the current behaviour?
Please chime in, and help improve this feature request.
Also how to make this this a proper feature request?
--
fsteff
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.09619 seconds
Home