Inconsistent/incorrect search results and resolution of includes (IEP-1124)

[ammaree]

I have been having hassles with the plugin over the last 4 months, most of which I have simply ignored or tried to work around, but it is now getting worse. Starting with Eclipse 2023-03/06/09 and with each version of the plugin, religiously updated, I am consistently getting incorrect resolution of definitions.

All my source code starts with the exact same #include "hal_config.h" to ensure the hardware and software platforms are completely defined. Within this header a specific hardware platform and firmware configuration is defined

After upgrading today to Eclipse 2023-12 and Plugin 2.11.1.202310270725 I am nog getting additional problems.
If I do a text search for #define appUSE_ACTUATORS Eclipse finds 11 occurrences but only lists 7 below for selection.

If I use F3 (Find Declarations) it finds 10 and not 11 with the important one (hal_dk41.h) missing:

To make things worse, the process of resolving headers either does not accurately parse the headers or symbols defined and/or does not assign the correct values. Following the chain from 1) the source code to 2) the top level header and then 3) the 2nd level header...
1: Source code:

2: Selection of the correct HW platform header

3: Definitions in the HW platform header

I have COMPLETELY removed all traces of Eclipse and the IDF plugin (including all my project configuration files) multiple times, reinstalled Eclipse according to the web site, symptoms remained the same. The code compiles correctly and functions as expected so I am 100% sure that cMake and the preprocessor/compiler finds the correct headers, definitions and values.

Lastly, the following warning/error occurs consistently:

Any suggestions?

[sigmaaa]

Hi @ammaree

Thank you for reporting this issue.

Lastly, the following warning/error occurs consistently:

this error could happen after switching to a different esp-idf without cleaning a project. To verify this scenario, you can check the project_description.json in the build folder and compare the "idf_path" property with the IDF_PATH environment variable (located in Preferences -> C/C++ -> Build -> Environment). If they are not the same, you can try to run full clean (right-click on project ESP-IDF: Project Full Clean) and build the project again.

[kolipakakondal]

Hi @ammaree Eclipse 2023-12 is not supported by the idf-eclipse-plugin yet. Please continue to use IEP plugin with the Eclipse CDT 2023-09.

I would also suggest switch to clangd indexer and editor features as eclipse cdt indexer is not maintained anymore and not compatible with the latest C/C++ 20 lang features. In future releases, we will automate these configuration steps.

[ammaree]

Hi @ammaree

Thank you for reporting this issue.

Lastly, the following warning/error occurs consistently:

this error could happen after switching to a different esp-idf without cleaning a project. To verify this scenario, you can check the project_description.json in the build folder and compare the "idf_path" property with the IDF_PATH environment variable (located in Preferences -> C/C++ -> Build -> Environment). If they are not the same, you can try to run full clean (right-click on project ESP-IDF: Project Full Clean) and build the project again.

I went far further that just a full clean, I deleted the './build' and './managed_components' directories as well as the 'dependencies.lock' and 'sdkconfig' files.

[sigmaaa]

Hi @ammaree
Thank you for reporting this issue.

Lastly, the following warning/error occurs consistently:

this error could happen after switching to a different esp-idf without cleaning a project. To verify this scenario, you can check the project_description.json in the build folder and compare the "idf_path" property with the IDF_PATH environment variable (located in Preferences -> C/C++ -> Build -> Environment). If they are not the same, you can try to run full clean (right-click on project ESP-IDF: Project Full Clean) and build the project again.

I went far further that just a full clean, I deleted the './build' and './managed_components' directories as well as the 'dependencies.lock' and 'sdkconfig' files.

Hi @ammaree,

do you still have a "Parsing Job..." exception after this?

[ammaree]

Yes I do, normally error comes up twice with exact same details

[sigmaaa]

Hi @ammaree,

one more question to clarify the root of the problem: after the build, did you compare the "idf_path" property from project_description.json with the IDF_PATH environment variable?

[ammaree]

Unable to answer your question. Recall that by the time I had received your message I had already cleaned out complete install to prove point on 2023-09. See next post on events since then… On 23/12/07, 12:28, "Denys Almazov" ***@***.******@***.***>> wrote: Hi @ammaree<https://github.com/ammaree>, one more question to clarify the root of the problem: after the build, did you compare the "idf_path" property from project_description.json with the IDF_PATH environment variable? — Reply to this email directly, view it on GitHub<#862 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAYT7GCUKLGS3DVTIDR6QWTYIGK5JAVCNFSM6AAAAABAJMDJRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBVGA4DIMJWGI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ammaree]

I think your latest changes, last couple of hours, has completely disabled ANY install of the Plugin.
I have completely cleaned out all traces of Eclipse and the plugin, even the Eclipse project directories and related files in my project directory and 4 (four) times tried to install Eclipse:
2x cpp-2023-09
2x cpp-2023-03
Every time from a complete clean base.
Every time used the same 'Stable" link for the Plugin and gone through the complete process, no errors.
Every time after the install there is NO SIGN of the plugin on the menu.

List of software to be installed and proof of the Eclipse version:

Updated info showing "modified" request:

After install and restart, installation details:

No sign of the plugin:

What now?

[sigmaaa]

Hi @ammaree,

we were able to find the root of the problem that caused this installation issue. The problem is that while updating/installing the plugin some dependencies are fetching from the latest plugins Eclipse 2023-12 and that is causing version incompatibility with the UI plugin. While we are working on a fix, I recommend you use Espressif-IDE which comes with Eclipse 2023-09+ IEP v2.11.1:
https://dl.espressif.com/dl/idf-eclipse-plugin/ide/Espressif-IDE-2.11.1-win32.win32.x86_64.zip

[ammaree]

Reasonably aware of what caused the problem, believe it was your rushed commit this morning to restrict the plugin installation on Eclipse 2023-12. It was done immediately after I raised my problem in spite of the fact that I made it clear I had tested my problem on 2023-03 and 2023-09, and only installed 2023-12 after all the tests.

I guess you did not look very carefully else you would have noticed that I use macOS not Windows so the link of no use.

[ammaree]

@sigmaaa
@kolipakakondal

And by the way, when I download using (https://dl.espressif.com/dl/idf-eclipse-plugin/ide/Espressif-IDE-macosx-cocoa-x86_64/latest) it also does not work....

[sigmaaa]

@sigmaaa @kolipakakondal

And by the way, when I download using (https://dl.espressif.com/dl/idf-eclipse-plugin/ide/Espressif-IDE-macosx-cocoa-x86_64/latest) it also does not work....

@ammaree

it looks like you are using Java 14 on Mac, but Java 17 or higher is required

[ammaree]

Using the Eclipse Installer the correct version of Java (17) is automatically installed. The problem, from what I can remember is that Eclipse does not recognise openjdk when installed with HomeBrew, and not aware of a fix for that. So without a solution installing Java 17 together with your Espressif-IDE for macOS it will remain a problem.

@igrr
I have personally lost at least 3 full days of work trying to get this going, probably ~2 weeks lost in total over last 2 months with all the hassles. Maybe it's time to invest the next 3 days into VSCode, just hope the Espressif plugin there is better. But I guess it is very unlikely (impossible?) to be worse than the Eclipse Plugin fiasco...

[ammaree]

Against our policy I installed Oracle Java 17.0.9 with the macOS Espressif-IDE, first build of a 100% clean project....