Community
Participate
Working Groups
Now that we allow for more advanced build behavior, we need a way to store configuration parameters. An example would be the command-line options to CMake or configure. My proposal is to have IBuilder inherit IHoldsOptions and hook it up just like ITool and IToolChain. Once that is complete, we'll need a way to override the IBuilder UI, but I'll save that for another bug. For now, setting the options in a template and using them in the build runner will do.
About to commit this. The change was pretty simple. I have made HoldsOption the superclass of Builder and hooked it up to the serialization and load routines. I have also added options as a child for builder in the buildDefinitions schema.
*** cdt cvs genie on behalf of dschaefer *** Bug 322794 Allow IBuilder to have IOptions. [*] buildDefinitions.exsd 1.46 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/all/org.eclipse.cdt.managedbuilder.core/schema/buildDefinitions.exsd?root=Tools_Project&r1=1.45&r2=1.46 [*] Builder.java 1.48 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/all/org.eclipse.cdt.managedbuilder.core/src/org/eclipse/cdt/managedbuilder/internal/core/Builder.java?root=Tools_Project&r1=1.47&r2=1.48 [*] IBuilder.java 1.20 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/all/org.eclipse.cdt.managedbuilder.core/src/org/eclipse/cdt/managedbuilder/core/IBuilder.java?root=Tools_Project&r1=1.19&r2=1.20
