Re: [cdt-dev] Scanner Info discovery for make projects

[Alex Chapiro <achapiro@xxxxxxx>]

Thanks,
I'm very familiar with this document, but it is not very useful in my 
point of view. Design specs stored in BUG 115935 are much more helpful 
for me.
BTW, about scattering of documentation. This document you referenced 
about is available in Europa bundle of help docs, but is not included 
into Ganimed  bundle. Why?

Alex

On 21/01/2009 7:48 AM, Kennedy, Stephen M (Steve) wrote:
> > -----Original Message-----
> > From: cdt-dev-bounces@xxxxxxxxxxx
> > [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Alex Chapiro
> > Sent: Tuesday, January 20, 2009 5:41 PM
> > To: CDT General developers list.
> > Subject: Re: [cdt-dev] Scanner Info discovery for make projects
> >
> > On 20/01/2009 12:02 AM, Alex Chapiro wrote:
> >      
> > > I'm tring to fix some problems in scanner context discovery
> > > implementation. I need it to customize CDT regular make
> > >        
> > project to our
> >      
> > > tool chain (GNU clone). Unfortunately documentation I found is
> > > definitely out of date (CDT 3),. That's why I cannot
> > >        
> > understand real
> >      
> > > developer's intention in some cases. One of the issues is a
> > >        
> > discovery
> >      
> > > profile. Specification describes two types of discovery:
> > >        
> > per project
> >      
> > > and per file. Technically each tool chain could have both
> > > implementations,  or just any one of two. If both implemented, user
> > > should be able to select any of them. Is it right? If yes,
> > >        
> > I don't see
> >      
> > > a natural way  how to do it.There is only one attribute in
> > >        
> > inputType
> >      
> > > element that connects particular tool to the particular scanner
> > > profile. Another option of interpretation is that developers didn't
> > > intend to let integrator to have both profiles for one tool
> > > simultaneously . May be?  The second subject of my concern is the
> > > possibility to select any of all defined profiles for any project
> > > using combo box on the  discovery options page (see field
> > >        
> > "Discovery
> >      
> > > profile".). Is it a bug ? When I look at this feature
> > >        
> > implementation,
> >      
> > > it seems to be done on purpose., so I feel myself to be confused.
> > > I don't say here about style of implementation  (like private
> > > constants in code) which is the cause of troubles in customization
> > > process, because  these are annoying but  mainly  solvable problems.
> > > More interesting to understand what is a correct behavior
> > >        
> > in this case.
> >      
> > > I'd appreciate clarification  of the issue or just opinion how it
> > > should work, or reference to more fresh document.;;Thanks,
> > >
> > > Alex.
> > > _______________________________________________
> > > cdt-dev mailing list
> > > cdt-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > >        
> > I found more recent  documentation  in Bugzilla report
> > 115935. I think that it would be much  more convenient if
> > design documentation and specs would be concentrated in one place.
> >
> > Thanks,
> >
> > Alex
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
> >      
>
> Alex,
>
> Also take a look at the "What's new in CDT Build System 4.0" entry in
> the "CDT Plug-in Developer Plug-in Guide" in Help->Help Contents.
>
> There are still at least a couple things missing from that: see
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=245685 .
>
> Steve Kennedy
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>