-
Notifications
You must be signed in to change notification settings - Fork 132
Sloeber V4.4.2 ESP32 Index bug #1610
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Hi Jantje,
Then I change something in properties, for example compile options. After, I try to rebuild Index many times with open and close several times Sloeber. Here is the log :
Sometimes, when I close Sloeber with the project open and then restart Sloeber, I have this window that freeze Sloeber then I need to kill Sloeber : |
Apart from
I noticed freezes when starting Sloeber as well but I never found the root cause. Note that in your case the freeze is at what I described before #1610 (comment) |
Hi,
Why he write : 0 sources, 0 headers ? |
I have seen this quite often. I do not know why CDT does that. After the logging you see
The entry above clearly states the discovery phase was not successfull |
Hi,
But these problems are not blocking. Note : I have this message on the log :
Also I noticed that if I delete the pdom file in "workspace.metadata.plugins\org.eclipse.cdt.core" directory can help the regeneration of the Index. Regards, |
Hi,
Regards, |
I'm currently working on #1126 that should fix this issue. |
Hi |
Hello, I encounter the same problem (Errors from missing imports for some of the framework/core components), but with slightly different symptoms. Then I tried to apply the suggestions here, but they did not work out, so I dug a little bit deeper and when enabling the console output I got
When I resolve "${recipe.cpp.o.CODAN}" in the environment I get The bash output of sloeber during the command is
If I try to compile it it fails as described in #1649 and I worked around that as I described in #1652. After that the project builds and uploads just fine. Its only the IDE code index that suggests errors. The same process works for Arduino Nano without showing these errors. |
@msebas If I have behavior like that the first thing I do is: go to the project properties->sloeber and verify the data is correct and then select apply/close. |
I took a look into the Sloeber configuration as suggested, but all options look correct. So I compared the options for a Arduino ESP32 Core 2.0.16 Test Project (which works fine out of the box) and a Arduino ESP32 Core 3.0.1 with the fixes mentioned in #1652 done to its environment. For the 2.0.16 Project everything works fine, but the 3.0.1 shows the result above. I did the following stepts to set up my test projects in an isolated Sloeber 4.4.3 on opensuse linux 15.5 (Kernel 5.14.21):
As I said for 2.0.16 it works and for 3.0.1 it fails. |
Have you seen #1652 |
Seems the indexer bug is fixed in V5 |
Hi,
I have a problem with the update of the Index.
When I change something in Sloeber properties of my ESP32 project, for example in Compile Options and then after "Apply and Close" I try to rebuild the Index, nothing is happening and all the lines of code is tagged red.
I need to close and reopen Sloeber many times to finally have the rebuild of the Index.
Any idea to solve this problem ?
thanks,
Lionel
The text was updated successfully, but these errors were encountered: