Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 360047

Summary:	AM_SILENT_RULES fouls scanner discovery
Product:	[Tools] CDT	Reporter:	Chris Stankevitz <chrisstankevitz>
Component:	cdt-autotools	Assignee:	Jeff Johnston <jjohnstn>
Status:	CLOSED WONTFIX	QA Contact:	Jeff Johnston <jjohnstn>
Severity:	minor
Priority:	P3	CC:	akurtakov, cdtdoug
Version:	8.1.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Chris Stankevitz

2011-10-05 17:43:21 EDT

Build Identifier: nightly build

If AM_SILENT_RULES is enabled, then scanner discovery and hence the eclipse indexer won't work.  You might want to add a check for it.

To work around, I remove AM_SILENT_RULES from configure.ac.  I believe there is a configure argument I can pass to disable, probably something like --disable-silent-rules.

Reproducible: Always

Comment 1 Jeff Johnston

2012-07-19 17:18:39 EDT

Automatic scanner discovery grabs information from the build output.  If you choose not to have build output, then you are essentially without a source of automatic discovery and must manually specify include paths yourself. 

I found a work-around to this listed on a developer's page whereby you do not have to alter your configure.ac file nor add a configuration option.  Simply override the build command in Properties->C/C++ Build and un-check the "Use default build command".  In place of "make", specify:  make V=1

I am closing this as WONTFIX.  There are multiple work-arounds to this problem (including manually specifying the Scanner info, using old build output, removing the macro, disabling, and using the V option for make).