Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 246907 - Remote scanner discovery
Summary: Remote scanner discovery
Status: RESOLVED FIXED
Alias: None
Product: PTP
Classification: Tools
Component: RDT (show other bugs)
Version: 2.1M2   Edit
Hardware: All All
: P2 enhancement (vote)
Target Milestone: 2.1M5   Edit
Assignee: Mike Kucera CLA
QA Contact: Greg Watson CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-10 14:21 EDT by Chris Recoskie CLA
Modified: 2011-05-14 06:38 EDT (History)
0 users

See Also:

Attachments
proposed patch (23.39 KB, patch)
2008-09-29 12:54 EDT, Mike Kucera CLA 		g.watson: iplog+
Details | Diff
View All 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 Chris Recoskie CLA 2008-09-10 14:21:03 EDT 
Right now we have no scanner discovery working for remote builds.  This will probably be tricky to do, as the existing scanner info/scanner discovery systems in CDT are a mess.
Comment 1 Mike Kucera CLA 2008-09-29 12:54:14 EDT 
Created attachment 113772 [details]
proposed patch

This patch gets remote scanner discovery to work, barely...


The patch adds a remote scanner discovery profile, but I cannot find any way to set it on a project automatically. The only way to get it to work is to manually select it from the Discovery Options property page. And even then it does not seem to work for Remote Makefile projects.

None of the collectors provided by CDT worked, they all just seemed to ignore the collected data. I ended up creating my own collector that writes the discovery paths and macros directly to the project description. So the paths don't show up as "built in", but at least they do show up and the indexer can use them. Also, after the discovery runs the paths don't show up right away. This is clearly a bug. If you close and reopen the project the paths show up.

The patch only provides scanner discovery for gcc. Most of it is reusable for xlc, but I think we would need a separate plugin for that.


Scanner Discovery in CDT is so broken, I think its a miracle I got this to work at all...
Comment 2 Mike Kucera CLA 2008-09-30 11:59:36 EDT 
Whoops, there are three calls to System.out.println() in ProjectDescriptionCollector.contributeToScannerConfig() that need to be removed.
Comment 3 Greg Watson CLA 2008-10-01 12:32:13 EDT 
I have applied this patch.
Comment 4 Chris Recoskie CLA 2008-10-01 18:37:17 EDT 
Mike,

I think we should mark this fixed and open some separate bugs for any of the remaining scanner info issues (which result from CDT).  If we can hack in some workarounds then we can track them separately.

What do you think?
Comment 5 Mike Kucera CLA 2008-10-02 10:45:41 EDT 
(In reply to comment #4)

Yeah, close the bug.
Comment 6 Chris Recoskie CLA 2008-10-09 09:43:09 EDT 
Ok I'm marking this as FIXED.  Mike, please open any new bugs you require to track any remaining issues.