Community
Participate
Working Groups
CommandBuilder has a CommandSearchLauncher class defined in it, which it uses to search for executables. See bug #145099 and bug #145737 for details on why it does this. I need to figure out a way to change the CommandSearchLauncher so that it respects the commandLauncher attribute of the builder.
This has been somewhat tricky due to the very screwy way that the internal builder is handled. When you pick the internal builder, it actually goes into the build model for your project and REMOVES the old builder, and puts in the internal builder instead. It's supposed to copy your settings over from the old builder when it does this. In the patch I'm working on, I have it so that it does this now. The problem is however that those settings disappear once you shut down the workbench and restart it. I've put code in the Builder class to serialize the command launcher settings, but for some reason they are not getting read when the project is loaded as the builder itself never gets loaded. Trying to figure out what the heck is going on here.
This will take a while to unravel, so I'm retargeting at 6.0.1
This bug was assigned and targeted at a now released milestone (or Future or Next that isn't being used by CDT). As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and mark the bug as resolved.
