Re: [cdt-dev] Managed Make Builder configurations

[Alex Chapiro <achapiro@xxxxxxx>]

Looks good.
Just a couple of questions

What is the meaning of projectType tag? Is it the same as abstract 
target now?

toolchain->archList exists in current model. But it works as a host 
toolchain filter and does nothing with target (sorry!) architecture. 
Does it have the same meaning in your model?

Just curious: is defaultExtension important to keep it separately from 
the artifact name? Or this is just for compatibility?

What do you think about the following little schema extension (this is 
once again about configuration attributes :-) )?

<projectType>
   <toolChain>
	....
   </toolChain>
   <configuration>
	....
       <!-- List of configuration attributes (target CPU, binary type ect.) -->
	<attribute
	    name="..."   
           id="..." >
           <!-- Attribute is alvays enumerated type (?). Its description includes the list
	     of possible values and how each value impacts toolchaun element; this is already 
            exists on configuration level -->	 
	    <attribValue
	        name="..."
               id="..." >
	        <toolReference
                 id="...">
              	     <optionReference
                       defaultValue="..."
                       id="...">
                    </optionReference>
		     ....
               </toolReference>                
		....
	    </attribValue>
	    ....
       </attribute>
	....
   </configuration>
</projectType>

As long as we are talking now about schema, I'm also advocating for 
small modifiction of optionCategory tag:

       <optionCategory
              owner="...."
              name="...."
              id="...."
           *   /class="....">/  *            
        </optionCategory>

to make it possible to provide customized option editors.


Treggiari, Leo wrote:

> > Thinking more about it, isn't it what is already in the managed build?
> > The toolchain is the target and configuration defined in the
> >    
> plugin.xml
>  
>
> > while the build settings is the target and configuration defined in
> >    
> the
>  
>
> > .cdtbuild. Could this understanding be correct or am I missing
> >    
> anything?
>  
>
> > I guess we are missing the os and architecture. Maybe it could just be
> > an attribute of a target (plugin.xml definition), couldn't it?
> >    
>
> Maybe, but I think there are 2 things wrong with the current Target:
>
> 1.  The name - "target" is confusing as to what it represents
> 2.  It is a combination of too may concepts
>
> I've been working on a proposal for Managed Build functionality for CDT
> 3.0.  I think the model needs some changes at the "top".  I'd like to
> get rid of "target" and have the model look like:
>
> <projectType>
>    <toolChain>
>        <tool>
>            the elements under "tool" remains unchanged
>        </tool>
>        <targetPlatform>
>            various target platform attributes...
>        </targetPlatform>
>    </toolChain>
>    <configuration>
>        <toolChainReference>
>            <toolReference>
>                the elements under "toolReference" remains unchanged 
>            </toolReference>
>        </toolChainReference>
>        <resourceConfiguration>
>            <toolReference>
>                the elements under "toolReference" remains unchanged 
>            </toolReference>
>        </resourceConfiguration>
>    </configuration>
> </projectType>
>
> The following target attributes would become projectType attributes:
> - isAbstract
> - parent
> - isTest
> The following target attributes would become configuration attributes:
> - artifactName
> - defaultExtension
> - cleanCommand
> The following target attributes would become toolChain attributes:
> - binaryParser
> - osList
> - archList
> - errorParsers
> - makeCommand
> - makeArguments
> - scannerInfoCollector
> - makefileGenerator
>
> I hope to have the full proposal in a week or so...
>
> Leo
>
> -----Original Message-----
> From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
> Behalf Of Pierre-Alexandre Masse
> Sent: Wednesday, June 09, 2004 7:41 PM
> To: cdt-dev
> Subject: RE: [cdt-dev] Managed Make Builder configurations
>
>
>  
>
> > Likewise, here at TimeSys.  We currently support configurations
> > as a combination of (build settings + toolchain).  Being able to
> > continue to support this once we move to CDT 2.0 is important
> > to us.
> >    
>
> Thinking more about it, isn't it what is already in the managed build?
> The toolchain is the target and configuration defined in the plugin.xml
> while the build settings is the target and configuration defined in the
> .cdtbuild. Could this understanding be correct or am I missing anything?
> I guess we are missing the os and architecture. Maybe it could just be
> an attribute of a target (plugin.xml definition), couldn't it?
>
>
> Pierre-Alexandre
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>