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

["Sennikovsky, Mikhail" <mikhail.sennikovsky@xxxxxxxxx>]

Hi Vladimir,

> 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.

Regards,
Mikhail

-----Original Message-----
From: Vladimir Prus [mailto:vladimir@xxxxxxxxxxxxxxxx] 
Sent: Monday, September 11, 2006 6:53 PM
To: Sennikovsky, Mikhail
Cc: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Rebuilding managed build project on properties
change

On Monday 11 September 2006 17:48, Sennikovsky, Mikhail wrote:

Hi Mikhail,

> > it appears that you're right about standard CDT. I've observed the
>
> problem
>
> > when testing "toolset-global options" -- options that affect not
just
>
> one
>
> > tool, but several of them. (I plan to sumbit that feature when it's
>
> more
>
> > ready)
>
> [Mikhail] Are you talking about some new functionality you are
> implementing? I'm asking because MBS already contains the shared
> (tool-chain) option functionality that in conjunction with the Option
> Value Handler mechanism is intended to be used for tool-chain wide
> setting modifications including modifying option for multiple tools.

Hmm, I did not find any when I was trying to get this functionality. 
Basically, I look for top-level option such a "Board". Such option
should be 
enumerated and each enumeration has separate command line options for 
compiler, assembler and linker. Something like:

    <option
           ........
           valueType="enumerated">
                  <enumeratedOptionValue
                                  ...........
                                  command.for.compiler=""
                                  command.for.linker=""
                                  command.for.assembler=""
                                  

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?

> > Can you tell me how changes in CDT tool properties currently cause a
> > rebuild,
> > so that I can figure out why the same code does not work for my new
> > options?
>
> [Mikhail] Most of the MBS model objects (Configuration, ToolChain,
Tool,
> Option) maintain the rebuild state that gets set to "rebuild" when the
> property of the object is changed.
> The rebuild states are analyzed and the set of resources affected by
the
> MBS Model changes is calculated. This is done by the MBS Build Model.
> The affected resources are then removed and rebuild.
> See org.eclipse.cdt.managedbuilder.buildmodel.BuildDescriptionManager
> class and the implementation of the
>
org.eclipse.cdt.managedbuilder.internal.core.GeneratedMakefileBuilder.bu
> ild() method.
> The build/rebuild itself is caused by the .cdtbuild file update that
is
> performed while persisting the MBS properties.

Thanks for the pointers. After some stepping though the code, I think
I'm 
starting to understand the logic. I'll look more and get back to this
list 
when I'm stuck again.

Thanks,
Volodya