Bug 381676 - [sd90] Cleaning out build output parser data
Summary: [sd90] Cleaning out build output parser data
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build (show other bugs)
Version: Next   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-build-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-05 05:54 EDT by Jonathan Watt CLA
Modified: 2020-09-04 15:20 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Watt CLA 2012-06-05 05:54:38 EDT
Can we have an easier way to strip out all the settings discovered by the build output parser, and reset the project back to how it was before running the build output parser and indexer? In "C/C++ General > Preprocessor Include Paths, Macros etc." the "Clear Entries" button is disabled. It would be good it this button was enabled for this purpose.
Comment 1 Andrew Gvozdev CLA 2012-06-05 09:41:56 EDT
"Clear Entries" button would be disabled in 2 cases: either provider has no entries or you are in the wrong context, i.e. provider is "Shared" in workspace. To clean shared provider use link "Workspace Settings". Otherwise "Clear Entries" works as you suggest.
Comment 2 Jonathan Watt CLA 2012-06-05 12:41:41 EDT
Say I open the project properties and go to C/C++ General > Preprocessor Include Paths..., and select the Entries Tab. There are indeed no entries under CDT GCC Build Output Parser, since build output parser data is currently associated with files, not directories. What I'm suggesting though is that even here, for the project properties, Clear Entries should be enabled so that I can clear the entries for all the files under the entire project.

The alternative of opening the properties individually for tens of thousands of files in the project to clear the settings for them individually is obviously impractical. I'm not sure if you're saying there is another way of doing what I want, but that way seems non-obvious enough to me that it would be worth enabling the Clear Entries button for directories and the project.
Comment 3 Andrew Gvozdev CLA 2012-06-05 13:03:47 EDT
(In reply to comment #2)
> Say I open the project properties and go to C/C++ General > Preprocessor Include
> Paths..., and select the Entries Tab. There are indeed no entries under CDT GCC
> Build Output Parser, since build output parser data is currently associated with
> files, not directories.
Right, in this context only entries for the current resource are cleared. If you want to clear all resources for the entire project go to Providers Tab and you can clear it in there.
Comment 4 Jonathan Watt CLA 2012-06-05 13:14:01 EDT
Hmm, I see what you mean. It doesn't let me clear the settings on a per-directory basis, and it's not so obvious I think. However, if you WONTFIX this bug then I guess I understand.
Comment 5 Andrew Gvozdev CLA 2012-06-05 13:22:24 EDT
(In reply to comment #4)
> Hmm, I see what you mean. It doesn't let me clear the settings on a
> per-directory basis, and it's not so obvious I think. However, if you WONTFIX
> this bug then I guess I understand.
I'll keep it for a while. I wanted but did not have enough time to take another closer look at UI. I can see that it can be confusing. Thanks for pointing that out.
Comment 6 Jonathan Watt CLA 2012-06-07 22:42:21 EDT
By the way, I've noticed that after clearing the settings in the Providers Tab (as you suggested in comment in 3) the indexer will start running when you close the project properties, even though my preferences are for the indexer to NOT run automatically.
Comment 7 Andrew Gvozdev CLA 2012-06-08 16:11:25 EDT
(In reply to comment #6)
> By the way, I've noticed that after clearing the settings in the Providers Tab
> (as you suggested in comment in 3) the indexer will start running when you close
> the project properties, even though my preferences are for the indexer to NOT
> run automatically.
Could you create a separate bug for that?
Comment 8 Jonathan Watt CLA 2012-06-08 17:58:04 EDT
I filed bug 382154.