Community
Participate
Working Groups
The Executables view gathers the list of executables from one or more providers that are responsible for searching through the open CDT projects and identifying the executables. It's expected the providers may dish out an answer based on which build configuration is active, as a configuration switch causes the view to re-query its providers. The stock provider in CDT (StandardExecutableProvider), however, answers with all binaries in all configurations. The end result is that the Executables view can quickly become very cluttered in an environment with many projects with many configurations. I've discussed this with Ken and he confirmed that the lack of filtering in StandardExecutableProvider is an oversight. So, I'll be adding the filtering. I'll also go one step further and update the JavaDoc to specify that providers should provide binaries relevant only to the active build configuration.
Reproducibility steps: 1. Create a simple project using the wizard. By default it gives you Debug and Release targets. 2. Build all configurations. 3. Open the executables view. Note that it shows the executables from both configurations. It should only show the one created by the active configuration
Created attachment 192691 [details] Fix
The cdt.core calling code looks fine to me John.
Fixed
*** cdt cvs genie on behalf of jcortell *** Bug 342096 - Executables view shows binaries for all build configurations instead of just the active ones [*] StandardExecutableProvider.java 1.9 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/all/org.eclipse.cdt.debug.core/src/org/eclipse/cdt/debug/core/executables/StandardExecutableProvider.java?root=Tools_Project&r1=1.8&r2=1.9 [*] IProjectExecutablesProvider.java 1.3 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/all/org.eclipse.cdt.debug.core/src/org/eclipse/cdt/debug/core/executables/IProjectExecutablesProvider.java?root=Tools_Project&r1=1.2&r2=1.3
