| Summary: | Problems with new build-before-launch launch configuration settings | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | John Cortell <john.cortell> |
| Component: | cdt-debug | Assignee: | cdt-debug-inbox <cdt-debug-inbox> |
| Status: | CLOSED INVALID | QA Contact: | Ken Ryall <ken.ryall> |
| Severity: | normal | ||
| Priority: | P3 | CC: | jamesblackburn+eclipse, pawel.1.piech |
| Version: | 7.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
John Cortell
Disregard #1. Misread the code. #2 still applies. John, there should be support for it in AbstractCLaunchDelegate, that is where we initially contributed it for our CDI-DE launches. Perhaps I screwed it up when I did my launch delegate refactoring a few months ago. (In reply to comment #2) > John, there should be support for it in AbstractCLaunchDelegate, that is where > we initially contributed it for our CDI-DE launches. Perhaps I screwed it up > when I did my launch delegate refactoring a few months ago. It wouldn't be the first time I overlooked something, or imagined I saw something that wasn't there. Could you double check? Ken, are you planning on getting to this before the RC4 build? If not, I can take it. AbstractCLaunchDelegate seems to be using the ICDTLaunchConfigurationConstants.ATTR_BUILD_BEFORE_LAUNCH setting just as AbstractCLaunchDelegate2 does. I did a quick test and this setting seems to work for me with a CDI launch. Huh. Sure enough, it's there. Not sure what I was smoking that day. I remember double-checking, too. But this was during my work on bug 309126 which had me making all sorts of changes to the CDI launcher (which I later chose to abandon). I guess I must have accidentally removed some code during that work; good thing I abandoned the CDI changes. |