Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Scanner discovery doesn't include build paths

This sounds similar to the fixes for

	https://bugs.eclipse.org/bugs/show_bug.cgi?id=416471
and	https://bugs.eclipse.org/bugs/show_bug.cgi?id=418406

The first (which has been committed) is modification to the New Project wizard.  The second (which is being modified
based on review comments) provides a new LanguageSettingsProvider.  There are links to the changesets from the review.
You might be able to use them as examples for your own fix.

-Andrew

On 13-10-09 05:15 AM, Azab, Mohamed wrote:
> Hi all,
> 
>  
> 
> We are working with CDT 8.2, and we have a CDT toolchain that has some include paths that gets changed depending on the
> project settings.
> 
> Those paths are added correctly to the build command, and the build operation works fine. But the scanner discovery
> 
> doesn't discover those paths and the editor shows ugly errors. To solve this issue, I had to add an extension point
> 
> to supply extra arguments to the scanner provider, but this solution is not generic, and it has to be modified whenever
> 
> something new appears. The problem is bigger in unmanaged build cases, where the toolchain is not specified, the scanner
> discovery
> 
> has no rule at all there. I thought that the scanner discovery should replicate the arguments used in build.
> 
>  
> 
> My question is; is there an available better and more generic way to solve this? Or are there plans to provide a
> solution for such cases soon?
> 
>  
> 
> Regards,
> 
> Mohamed Azab
> 
> 
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> 



Back to the top