Bug 314460

Description John Cortell 2010-05-26 09:38:04 EDT

While working on bug 309126, it was noticed that the Map of arguments set to BuildManager for a build is suspiciously thin when the build is invoked by right clicking on the project and selecting

   Build Configurations > Build Selected...

and choosing a particular configuration. James thought this may be a bug and so I've filed this report. See second paragraph in

   https://bugs.eclipse.org/bugs/show_bug.cgi?id=309126#c18

I set a breakpoint in BuildManager.basicBuild(int, IncrementalProjectBuilder, Map, MultiStatus, IProgressMonitor) and noticed the following arg(Map) contents in each scenario. The "Build Project" scenario is simply right clicking on the project and hitting "Build Project.

=== args contents for Build Project ===
org.eclipse.cdt.make.core.enableCleanBuild=true
org.eclipse.cdt.make.core.append_environment=true
org.eclipse.cdt.make.core.contents=org.eclipse.cdt.make.core.activeConfigSettings
?name?=
org.eclipse.cdt.make.core.buildLocation=${workspace_loc:/helloworld/Debug}
org.eclipse.cdt.make.core.enableAutoBuild=false
org.eclipse.cdt.make.core.useDefaultBuildCmd=true
org.eclipse.cdt.make.core.buildArguments=
org.eclipse.cdt.make.core.buildCommand=make
org.eclipse.cdt.make.core.enableFullBuild=true
org.eclipse.cdt.make.core.stopOnError=true

=== args contents for Build Selected (configuration) ===
org.eclipse.cdt.make.core.configurationIds=cdt.managedbuild.config.gnu.mingw.exe.debug.1107845113|
org.eclipse.cdt.make.core.contents=org.eclipse.cdt.make.core.configurationIds