Re: [cdt-dev] How to invalidate cached scanner info?

[Anna Dushistova <anna_dushistova@xxxxxxxxxx>]

On Jun 11, 2010, at 10:42 PM, Doug Schaefer wrote:

> Join the club :). Are you talking about the contents of the .sc file?
> Or the stuff cached in DiscoveredPathInfo?
> 

I think both. What I need is to change my options(say, toolchain prefix) and see only new include paths under "includes".
I think we all agree that showing includes for, say, mips doesn't make sense when we are working with arm now.

> My struggles came from the later but was fixed in RC4 by re-adding a
> line in the ScannerConfigBuilder that cleared it for us.
> 
> BTW, I'm doing something similar for Android, but without cloning. If
> there are changes needed to support cross compilers, we should be
> doing that in the core, since host compilers is just a special case of
> that, i.e. without the prefix.
> 
> On Fri, Jun 11, 2010 at 2:25 PM, Anna Dushistova
> <anna_dushistova@xxxxxxxxxx> wrote:
>> Hi All,
>> 
>> is there any way to invalidate the cached scanner info that is stored in org.eclipse.cdt.make.core/ ?
>> I want to clean it each time I have settings changed because this information is not relevant anymore.
>> My toolchain is gcc based and I have my own scanner implementation which is just a clone of Linux gcc one.
>> 
>> Thanks!
>> Anna._______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev