Bug 373862 - [Scanner Discovery] Should emit a warning when it doesn't understand build output.
Summary: [Scanner Discovery] Should emit a warning when it doesn't understand build ou...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build (show other bugs)
Version: 8.0   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: cdt-build-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-10 07:12 EST by Kees-Jan Dijkzeul CLA
Modified: 2020-09-04 15:18 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kees-Jan Dijkzeul CLA 2012-03-10 07:12:06 EST 
Build Identifier: Version: Indigo Service Release 1 Build id: 20110916-0149

In Bug 373198, Andrew Overholt requested that I file this bug.

I learned (in Bug 373198) that the indexer tries to interpret the output generated by make, looking for include paths and defines. This assumes that make logs the compile commands it invokes, which is not the case for all Makefile projects.

I propose that the indexer emits a warning if it does not finds any compiler invocations in the make output.

Additionally (alternatively?) a warning could also be emitted if the build is successful, and yet unresolved inclusions remain. This also is an indication that discovery failed somewhere.

Reproducible: Always