Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360047 - AM_SILENT_RULES fouls scanner discovery
Summary: AM_SILENT_RULES fouls scanner discovery
Status: CLOSED WONTFIX
Alias: None
Product: CDT
Classification: Tools
Component: cdt-autotools (show other bugs)
Version: 8.1.0   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Jeff Johnston CLA
QA Contact: Jeff Johnston CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-05 17:43 EDT by Chris Stankevitz CLA
Modified: 2012-07-19 17:18 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Stankevitz CLA 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 CLA 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).