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

Bug 341455

Summary:	Problems with the Discovery Options interface and its documentation
Product:	[Tools] CDT	Reporter:	Jonathan Watt <jwatt>
Component:	cdt-build	Assignee:	cdt-build-inbox <cdt-build-inbox>
Status:	NEW ---	QA Contact:	Jonah Graham <jonah>
Severity:	normal
Priority:	P3	CC:	cdtdoug, yevshif
Version:	7.0.2
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Jonathan Watt

2011-03-31 05:26:32 EDT

In this bug report I use the term "ref doc" to refer to:

http://help.eclipse.org/helios/topic/org.eclipse.cdt.doc.user/reference/cdt_u_prop_build_discovery.htm

For "Report path detection problems" the ref doc does not say where those problems will be reported, so you've given no clue where to look for them.

The ref doc does not say what a "discovery profile" is. Most problematic is that it does not explain the various options in the "Discovery profile" drop down menu, what they are for, what the difference is between them, why you might choose one over another, or what the consequences of doing so will be.

The ref doc does not say what the "generated scanner info command" is for, so it's a bit of a mystery as to why you'd want to enable/disable it, or how you use it and its options.

I've checked out the source via CVS, so if someone can shed some light on any of the above I'd be happy to propose some patches to the documentation.

Comment 1 Andrew Gvozdev

2011-03-31 12:19:29 EDT

Scanner discovery in CDT is difficult to master or maintain. We are working on an alternative even if admittedly slow. See bug 290631.

Comment 2 Jonathan Watt

2011-03-31 17:09:09 EDT

Thanks for the pointer.

Since it looks like it'll be another year or so before a release of Eclipse has the new scanner discovery stuff, I'd still be interested in any any thoughts on the above from anyone though.