Re: [cdt-dev] Trying to implement a scanner configuration discovery pro

[Doug Schaefer <cdtdoug@xxxxxxxxx>]

Don't have much to provide, sorry. I feel your pain. I've been trying to get the scanner discovery to work correctly for the new GCC cross-compiler support and am really struggling with it. Hopefully someone out there has had more success?

Doug.

On Thu, May 7, 2009 at 1:58 PM, Anderson, Glen <Glen.Anderson@xxxxxxxxxx> wrote:

                Hi all,

 

                Currently I’m trying to implement a plugin that adds built-in include paths, library paths and preprocessor definitions to the Paths and Symbols preference page in our CDT based product (currently developing against 6.0 M6).  From the (likely outdated) documentation that I’ve been able to find it seems like extending the org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile extension point and providing my own implementation of IScannerInfoCollector and IScannerInfoProvider is the way to go.

 

                Having done that I can see that my provider is being called appropriately and is adding the correct information to the collector.  The problem that I’m seeing is that at no point is IScannerInfoCollector.getCollectedScannerInfo() ever called.  Grepping through the entire CDT source tree seems to reveal that there are only two instances of this method being called, both of which are in internal GCC related implementations and neither of which are actually asking for ScannerInfoTypes.INCLUDE_PATHS or ScannerInfoTypes.SYMBOL_DEFINITIONS.

 

                Has this mechanism been deprecated or is there maybe something else that I’m missing?  Does anyone know of a better way to accomplish this?

 

                Thanks,

                Glen

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev