[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.tools.cdt] Re: Removing Build Options In CDT 
Hello Derek,

Thanks for the response, hopefully you can help me out a bit, how will I tell the option in the toolchain, the name of the applicabilityCalculator
class I add to my plugin without changing the CDT tool setting (and therefore changing the cdt plugin.xml) ?

Is there a way of using an ID somehow ?

Marcus.

Option #1 does what you want. You just supply it as an additional
class with your plugin. No changes to CDT required.

CDT wrote:

Hi,

I have sucessfully added a toolchain, and some tools
(compiler/linker/assembler) to the CDT using the extension point
(org.eclipse.cdt.managedbuilder.core.buildDefinitions). They are
based upon the existing MinGW tools.

My compiler for example uses the superclass
cdt.managedbuild.tool.gnu.c.compiler.mingw.base. This ID in the
managedbuilder.gnu.ui plugin represents the MinGW C Compiler, this in
turn uses the superclass cdt.managedbuild.tool.gnu.c.compiler. The
gnu C Compiler has many build options, most of which I want to keep.

However I want to remove some options, so I can either...

1. Use the applicabilityCalculator option to implement the
IOptionApplicability, to make it not visible
2. Delete the option altogether from CDT (thus affecting all
compilers)
3. Re-implement the entire toolchain (ie dont use
cdt.managedbuild.tool.gnu.c.compiler.mingw.base superclass)
Looking at options 1 and 2, I will have to make sure my customers
always get their CDT version from me (which will include my changes),
option 3 I have had very limited sucess. So my question is can I
remove some options for my tool, without affecting the underlying CDT
by implementing an interface somewhere that doesn't require a change
to the CDT ?

Marcus.