Re: [cdt-dev] Rebuilding managed build project on properties change

[Vladimir Prus <vladimir@xxxxxxxxxxxxxxxx>]

On Monday 11 September 2006 20:37, Sennikovsky, Mikhail wrote:

Hi Mikhail,

> > If you're saying that this is supported in standard CDT, can you point
>
> me > to
>
> > the docs or code where I can learn more?
>
> Take a look at https://bugs.eclipse.org/bugs/show_bug.cgi?id=90481.

If I'm reading that document correctly, in order to implement toochain-level 
options I'd need the following:

   1. Implement new ValueHandler.
   2. Define new option, specifying the ValueHandle
   3. Make my ValueHandler store options somewhere.
   4. Derive from GnuMakefileGenerator and modify it so that it adds extra
   command line options to tools, depending on values set in (3)
   5. Arrange for my project to use my class derived from  
   GnuMakefileGenerator, instread of GnuMakefileGenerator itself, which can be
   done by editing the 'buildfileGenerator' attribute of the 'builder' element
   of the <toolChain> element for my project type.

Is the right approach? Is there a better one?

Assuming it is, how will auto-clean work for global options. The 
Configuration.needsRebuild method appear to ignore global options completely, 
so even if I edit a global option, Configuration.needsRebuild will return 
false.

Likewise, I want global option to affect options of several tools. If that 
logic is contained in a class derived from GnuMakefileGenerator, then a 
change in global option won't case Tool.needsRebuild() for the affected tool 
to return true. Should I call setRebuildState() manually?

Thanks again,
Volodya