Re: [cdt-dev] Scanner discovery doesn't include build paths

[Andrew Gvozdev <angvoz.dev@xxxxxxxxx>]

Hi Vladimir,

Most of the options that MBS defines are not useful for scanner discovery. I added a new flag to an option in toolchain definition (buildDefinitions extension point) to indicate that the option should be used by scanner discovery, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=404913#c6.

Currently options under category "Dialect" are marked as such, "Language standard" and free text field "Other dialect flags". Keep in mind that the language settings provider needs to belong to configuration (i.e. be non-global) to get access to configuration options.

Thanks,

Andrew

On Wed, Oct 23, 2013 at 2:41 AM, Vladimir Prus <vladimir@xxxxxxxxxxxxxxxx> wrote:

On 09.10.2013 14:17, Vladimir Prus wrote:

On 09.10.2013 14:11, scalpel4k wrote:

Hi Mohamed,

have you tried CDT from master? A lot of things have changed for the better recently. I don't know whether those changes have been
backported to 8.2.1.

Hi Mich,

are there any specific commits that would make scanner discovery obtain information from MBS about compiler command lines?

Ping? Can somebody authoratively confirm that that in master, scanner discovery will run the compiler with exactly the same
options that MBS would use? Andrew, do you know?

--
Vladimir Prus
CodeSourcery / Mentor Graphics
http://www.mentor.com/embedded-software/