Community
Participate
Working Groups
There is a new way that launch configs can be mapped to resource so that when the debug or run buttons are pressed, the current selection determines what config to launch. Feedback from users tell us that launch configs are very confusing and they really want to press these buttons and have Eclipse figure out the proper config to run. With managed build, we should be able to create the default configuration and hook it up using the platform mechanisms. We should also be able to alter the default config as the default build config changes.
If I follow correctly, if resource type can be mapped to specific launch type, so how would Managed Build know which launch type to use?
(In reply to comment #0) > Feedback from users tell us that launch configs are very confusing and they > really want to press these buttons and have Eclipse figure out the proper > config to run. I agree. > With managed build, we should be able to create the default configuration and > hook it up using the platform mechanisms. We should also be able to alter the > default config as the default build config changes. What about this strategy: - When a launch config is created, try to guess the project from the current selection. - For managed make projects the executable binary is automatically determined from the current build configuration and the artifact name. - This behavior can be deselected in favor of the old behavior i.e. the launch config just relies on the user input in the "C/C++ Application" text box. That would mean to add a checkbox "Manually specify application". It would be deselected by default and would, in this case, grays out the "C/C++ Application" text box. If it is selectd the user must specify the path to the app in the text box just as it is the case now. > There is a new way that launch configs can be mapped to resource so that when I do not even see that any new mechanisms are required. Not that I am against it, of course :-)
Related to the work for 154280.
Still tracking changes in debug platform launch scheme, moved to M6.
I've been reworking the current launch shortcut to work with the new launch support but don't have it ready to commit just yet, maybe next week. After thats in it may be more apparent how we can better integrate it with info from the active toolchain and this will become a duplicate of bug 179755.
Hey Ken, can you attach a patch of what you've got. I don't mind spending time on it Friday to try and get it in, even if it isn't totally working. I'd really like to get the user experience cleaned up for RC0. We have it now with the project templates and I'd like to get single push debugging working too.
Actually I'm probably doing the same thing you are. As I've just stumbled into the shortcut code. The changes I've made in the debugger tab need to go here too. I will mark this as a duplicate. *** This bug has been marked as a duplicate of bug 179755 ***
