RE: [cdt-dev] Looking for a quick way to define tools in MBS

["dmsubs" <dmsubs@xxxxxxxxxxxxx>]

Chris,

Thanks for the pointer. I have now defined an abstract tool that I then use
as a superclass for my actual tool definitions. It all appears as I want in
the Properties dialog.

But, I now have a new problem - the tool settings don't persist. That is, in
a project that uses my tool, I can change my tool options in the Properties
dialog, but when I close the dialog, and reopen it, my changes have
disappeared.

I've tried to compare my plugin.xml with
org.eclipse.cdt.managedbuilder.gnu.ui/plugin.xml but I can't find anything
obviously wrong. Any ideas?

Thanks again!

---
Derek  

> -----Original Message-----
> From: Recoskie, Chris [mailto:crecoskie@xxxxxx] 
> Sent: 07 December 2005 16:37
> To: dmsubs@xxxxxxxxxxxxx
> Subject: RE: [cdt-dev] Looking for a quick way to define tools in MBS
> 
> You can use the superclass attribute on tools as well.   So 
> if you have
> a Release configuration, you would have a release toolchain, 
> which has tools under it (they presumably have superclasses 
> so you don't have to specify your tool all over again).  You 
> can specify superclassed options under those tools to 
> override any defaults you wish.
> 
> Take a look at 
> org.eclipse.cdt.managedbuilder.gnu.ui/plugin.xml, that should 
> be a good example for you.
> 
> ___________________________________________
>  
> Chris Recoskie
> Software Designer
> Texas Instruments, Toronto
> http://eclipse.org/cdt
>  
>  
> 
> > -----Original Message-----
> > From: dmsubs [mailto:dmsubs@xxxxxxxxxxxxx]
> > Sent: Wednesday, December 07, 2005 11:06 AM
> > To: Recoskie, Chris; 'CDT General developers list.'
> > Subject: RE: [cdt-dev] Looking for a quick way to define 
> tools in MBS
> > 
> > Chris,
> > 
> > Thanks. That *almost* does what I want.
> > 
> > I've defined a tool complete with optionCategories and options etc
> which I
> > can re-use by specifying it's id as a superclass for tools in other 
> > configurations. This part works.
> > 
> > However, I have a debug option (-g) defined as one of the 
> options. How
> can
> > I
> > make it's value true (i.e. add the -g flag) in debug configurations
> but
> > make
> > it's value false in non-debug configurations, again, 
> without having to 
> > define the whole hierarchy?
> > 
> > Thanks for your help!
> > 
> > ---
> > Derek
> > 
> > > -----Original Message-----
> > > From: Recoskie, Chris [mailto:crecoskie@xxxxxx]
> > > Sent: 06 December 2005 19:03
> > > To: dmsubs@xxxxxxxxxxxxx; CDT General developers list.
> > > Subject: RE: [cdt-dev] Looking for a quick way to define tools in
> MBS
> > >
> > > Yes... use the superClass attribute on whichever element 
> you need to 
> > > replicate, and specify the ID of the element you wish to 
> subclass.  
> > > You can override whichever elements/attributes you wish, 
> and leave 
> > > the rest as defaults.
> > >
> > > How exactly you design the hierarchy of your "classes" is 
> dependant 
> > > upon the details of the project types and configurations you're 
> > > creating
> > >
> > > ___________________________________________
> > >
> > > Chris Recoskie
> > > Software Designer
> > > Texas Instruments, Toronto
> > > http://eclipse.org/cdt
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: cdt-dev-bounces@xxxxxxxxxxx
> > > [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> > > On
> > > > Behalf Of dmsubs
> > > > Sent: Tuesday, December 06, 2005 1:54 PM
> > > > To: 'CDT General developers list.'
> > > > Subject: [cdt-dev] Looking for a quick way to define 
> tools in MBS
> > > >
> > > > Hi,
> > > >
> > > > I'm defining a new tool plugin to MBS. I need to define the
> > > same tool,
> > > > inputType, outputType, optionCategory(s) and option(s) 
> in several 
> > > > different projectTypes and configurations.
> > > >
> > > > Using only plugin.xml, the tool has 1 inputType, 1 
> outputType, 5 
> > > > optionCategories and over 20 options. I need to replicate the
> whole
> > > > edifice
> > > > 6 times (3 platforms with 2 configurations on each). I'm doing
> this
> > > with
> > > > cut
> > > > and paste... This can lead to errors and is a nightmare to
> maintain.
> > > >
> > > > So, my question is, is there a way I can define a tool with its 
> > > > optionCategories, options etc so that I can then reuse them
> without
> > > having
> > > > to duplicate?
> > > >
> > > > Thanks,
> > > >
> > > > ---
> > > > Derek
> > > >
> > > > _______________________________________________
> > > > cdt-dev mailing list
> > > > cdt-dev@xxxxxxxxxxx
> > > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
>