Skip to content

Check for cdt indexer options #825

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jantje opened this issue Sep 18, 2017 · 7 comments
Closed

Check for cdt indexer options #825

jantje opened this issue Sep 18, 2017 · 7 comments
Assignees

Comments

@jantje
Copy link
Member

jantje commented Sep 18, 2017

With more and more functions relying on a "good working" of the indexer it is a good idea to check whether the indexer settings are "as expected by sloeber".
My settings are:
afbeelding
note that index source files not included in the build must be turned off.
People using multiple configurations should use the active configuration to build the indexer.
I don't think other settings are really important.
Well indexer on is, should test what Sloeber does when the indexer is off.

@jantje jantje added domain: configuration Configuring Sloeber does not work as docummented importance: improvement request OS: all labels Sep 18, 2017
@jantje jantje self-assigned this Sep 18, 2017
@jantje
Copy link
Member Author

jantje commented Sep 18, 2017

apparently index unused headers must be turned off as well.

jantje pushed a commit that referenced this issue Nov 4, 2017
user must change the warnings.
@jantje
Copy link
Member Author

jantje commented Nov 4, 2017

I added checks for these values directly reading the instancescope.
The user needs to change the value in windows->preferences->c/c++->indexer
This warning can not be disabled

@climategadgets
Copy link

This behavior breaks at least ESP-IDF projects.

Changing IDE configuration, especially without a warning, especially from default settings, and especially if Sloeber installation failed because of transient errors is... time consuming for the unaware.

It would be a welcome feature if the installer asked nicely to change this setting, and warned the user about consequences of not changing it. And only after making sure that all the prerequisites were successfully obtained.

@jantje
Copy link
Member Author

jantje commented Apr 13, 2020

@climategadgets Not sure what you are talking about.
The indexer does not influence the building of the project.
If the indexer includes unwanted libraries you can disable this feature in preferences->arduino.

As to

It would be a welcome feature if the installer asked nicely to change this setting,

  1. This issue is about sloeber checking these values and telling you "nicely" at startup when Sloeber thinks these are set wrongly.
  2. I think Sloeber has no lessons to learn from you in regards to "asking nicely"

@climategadgets
Copy link

The installer immediately changes the indexer settings without giving any indication that it is going to do so. The side effect of that is Eclipse immediately loses track of references, all open files get red marks, and code cannot be navigated anymore.

@uzi18
Copy link
Contributor

uzi18 commented Apr 13, 2020

@jantje have same situation in time of editing file indexer marks all with red and sometimes recover sometimes not, so code completion works unreadable.
Give me some hints how to investigate this?

@jantje
Copy link
Member Author

jantje commented Apr 13, 2020

@uzi18 First is always: rebuild the index.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants