Eclipse plugin for ESP-IDF CMake based projects (4.x and above)
Eclipse plugin for ESP-IDF CMake based projects (4.x and above)
Hi folks,
Espressif provide IDF Eclipse Plugins aiming to provide better tooling capabilities, which simplifies and enhances standard Eclipse CDT for developing and debugging ESP32 IoT applications.
Install
Install Tools
Templates
Build
SDK Configurator
CMake Editor and more and more
read more how you install, setup, config and other.
best wishes
rudi
Espressif provide IDF Eclipse Plugins aiming to provide better tooling capabilities, which simplifies and enhances standard Eclipse CDT for developing and debugging ESP32 IoT applications.
Install
Install Tools
Templates
Build
SDK Configurator
CMake Editor and more and more
read more how you install, setup, config and other.
best wishes
rudi
-------------------------------------
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪
- PaulVdBergh
- Posts: 58
- Joined: Fri Feb 23, 2018 4:45 pm
- Location: Brasschaat, Belgium
Re: Eclipse plugin for ESP-IDF CMake based projects (4.x and above)
Hi All,
I followed the setup as described in your post. When I try to compile the Hello_world example, I get the following errors:
What am I missing?
ps : I installed a fresh Debian 10.1.0 image in a Virtualbox running under Win10.
I'm keen on reading your answer.
Paul
I followed the setup as described in your post. When I try to compile the Hello_world example, I get the following errors:
Code: Select all
Building in: /home/paulvdbergh/eclipse-workspace/Hello_world/build
cmake -G Ninja -DCMAKE_TOOLCHAIN_FILE=/home/paulvdbergh/esp/esp-idf/tools/cmake/toolchain-esp32.cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DIDF_TARGET=esp32 /home/paulvdbergh/eclipse-workspace/Hello_world
/usr/lib/git-core/git-submodule: 7: /usr/lib/git-core/git-submodule: basename: not found
/usr/lib/git-core/git-submodule: 7: /usr/lib/git-core/git-submodule: sed: not found
/usr/lib/git-core/git-submodule: 86: /usr/lib/git-core/git-sh-setup: sed: not found
/usr/lib/git-core/git-submodule: 86: /usr/lib/git-core/git-sh-setup: basename: not found
/usr/lib/git-core/git-submodule: 332: /usr/lib/git-core/git-sh-setup: uname: not found
-- Project is not inside a git repository, or git repository has no commits; will not use 'git describe' to determine PROJECT_VER.
-- Project version: 1
-- Building ESP-IDF components for target esp32
-- Checking Python dependencies...
-- Configuring incomplete, errors occurred!
See also "/home/paulvdbergh/eclipse-workspace/Hello_world/build/CMakeFiles/CMakeOutput.log".
CMake Error at /home/paulvdbergh/esp/esp-idf/tools/cmake/build.cmake:252 (message):
Some Python dependencies must be installed. Check above message for
details.
Call Stack (most recent call first):
/home/paulvdbergh/esp/esp-idf/tools/cmake/build.cmake:378 (__build_check_python)
/home/paulvdbergh/esp/esp-idf/tools/cmake/project.cmake:341 (idf_build_process)
CMakeLists.txt:6 (project)
cmake --build . -- -v
ninja: error: loading 'build.ninja': No such file or directory
Build complete (0 errors, 0 warnings): /home/paulvdbergh/eclipse-workspace/Hello_world/build
ps : I installed a fresh Debian 10.1.0 image in a Virtualbox running under Win10.
I'm keen on reading your answer.
Paul
Re: Eclipse plugin for ESP-IDF CMake based projects (4.x and above)
PaulVdBergh wrote: ↑Tue Sep 17, 2019 4:11 pmHi All,
I followed the setup as described in your post. When I try to compile the Hello_world example, I get the following errors:
What am I missing?Code: Select all
Building in: /home/paulvdbergh/eclipse-workspace/Hello_world/build cmake -G Ninja -DCMAKE_TOOLCHAIN_FILE=/home/paulvdbergh/esp/esp-idf/tools/cmake/toolchain-esp32.cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DIDF_TARGET=esp32 /home/paulvdbergh/eclipse-workspace/Hello_world /usr/lib/git-core/git-submodule: 7: /usr/lib/git-core/git-submodule: basename: not found /usr/lib/git-core/git-submodule: 7: /usr/lib/git-core/git-submodule: sed: not found /usr/lib/git-core/git-submodule: 86: /usr/lib/git-core/git-sh-setup: sed: not found /usr/lib/git-core/git-submodule: 86: /usr/lib/git-core/git-sh-setup: basename: not found /usr/lib/git-core/git-submodule: 332: /usr/lib/git-core/git-sh-setup: uname: not found -- Project is not inside a git repository, or git repository has no commits; will not use 'git describe' to determine PROJECT_VER. -- Project version: 1 -- Building ESP-IDF components for target esp32 -- Checking Python dependencies... -- Configuring incomplete, errors occurred! See also "/home/paulvdbergh/eclipse-workspace/Hello_world/build/CMakeFiles/CMakeOutput.log". CMake Error at /home/paulvdbergh/esp/esp-idf/tools/cmake/build.cmake:252 (message): Some Python dependencies must be installed. Check above message for details. Call Stack (most recent call first): /home/paulvdbergh/esp/esp-idf/tools/cmake/build.cmake:378 (__build_check_python) /home/paulvdbergh/esp/esp-idf/tools/cmake/project.cmake:341 (idf_build_process) CMakeLists.txt:6 (project) cmake --build . -- -v ninja: error: loading 'build.ninja': No such file or directory Build complete (0 errors, 0 warnings): /home/paulvdbergh/eclipse-workspace/Hello_world/build
ps : I installed a fresh Debian 10.1.0 image in a Virtualbox running under Win10.
I'm keen on reading your answer.
Paul
hi paul
note, the plugin is for CMake based projects (4.x and above)
it means, you need ESP-IDF 4.x and above
..
it looks like
Code: Select all
..
Some Python dependencies must be installed. Check above message for details.
..
did you install these tools and other tools after the install?
you need it first.
cause it start at 4.x perhabs you have a note from the readme first
Install Prerequisites
example:
Code: Select all
sudo apt-get install git wget libncurses-dev flex bison gperf python python-pip python-setuptools python-serial python-click python-cryptography python-future python-pyparsing python-pyelftools cmake ninja-build ccache
CMake version 3.5 or newer is required for use with ESP-IDF.
Older Linux distributions may require updating, enabling of a “backports” repository, or installing of a “cmake3” package rather than “cmake”.
also python says, you must install few dependenies,
it is in the requirements.txt file example here
hope this helps for orientation and further steps.
best wishes
rudi
-------------------------------------
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪
- PaulVdBergh
- Posts: 58
- Joined: Fri Feb 23, 2018 4:45 pm
- Location: Brasschaat, Belgium
Re: Eclipse plugin for ESP-IDF CMake based projects (4.x and above)
Hi Rudi,
Thanks for your response.
Executing the folowing command give this result :
So I think I have the right tools installed ? (The documentation mentions Python 3.7, my install reports 2.7, is this the problem?)
How can I use the esp-idf/requirements.txt file to make it usefull ?
Thanks for your appreciated response,
Paul
Edit:
Thanks for your response.
Executing the folowing command give this result :
Code: Select all
paulvdbergh@debian-10:~$ sudo apt-get install git wget libncurses-dev flex bison gperf python python-pip python-setuptools python-serial python-click python-cryptography python-future python-pyparsing python-pyelftools cmake ninja-build ccache
Reading package lists... Done
Building dependency tree
Reading state information... Done
bison is already the newest version (2:3.3.2.dfsg-1).
ccache is already the newest version (3.6-1).
cmake is already the newest version (3.13.4-1).
flex is already the newest version (2.6.4-6.2).
git is already the newest version (1:2.20.1-2).
gperf is already the newest version (3.1-1).
libncurses-dev is already the newest version (6.1+20181013-2+deb10u1).
ninja-build is already the newest version (1.8.2-1).
python-pyparsing is already the newest version (2.2.0+dfsg1-2).
python-serial is already the newest version (3.4-4).
python-click is already the newest version (7.0-1).
python-cryptography is already the newest version (2.6.1-3).
python is already the newest version (2.7.16-1).
python-future is already the newest version (0.16.0-1).
python-pip is already the newest version (18.1-5).
python-pyelftools is already the newest version (0.25-2).
python-setuptools is already the newest version (40.8.0-1).
wget is already the newest version (1.20.1-1.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
paulvdbergh@debian-10:~$
Code: Select all
paulvdbergh@debian-10:~$ python --version
Python 2.7.16
Thanks for your appreciated response,
Paul
Edit:
Code: Select all
paulvdbergh@debian-10:~$ python3.7 --version
Python 3.7.4
paulvdbergh@debian-10:~$
Re: Eclipse plugin for ESP-IDF CMake based projects (4.x and above)
Hi Paul,PaulVdBergh wrote: ↑Tue Sep 17, 2019 4:11 pmWhen I try to compile the Hello_world example, I get the following errors:
Code: Select all
Building in: /home/paulvdbergh/eclipse-workspace/Hello_world/build cmake -G Ninja -DCMAKE_TOOLCHAIN_FILE=/home/paulvdbergh/esp/esp-idf/tools/cmake/toolchain-esp32.cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DIDF_TARGET=esp32 /home/paulvdbergh/eclipse-workspace/Hello_world /usr/lib/git-core/git-submodule: 7: /usr/lib/git-core/git-submodule: basename: not found /usr/lib/git-core/git-submodule: 7: /usr/lib/git-core/git-submodule: sed: not found /usr/lib/git-core/git-submodule: 86: /usr/lib/git-core/git-sh-setup: sed: not found /usr/lib/git-core/git-submodule: 86: /usr/lib/git-core/git-sh-setup: basename: not found /usr/lib/git-core/git-submodule: 332: /usr/lib/git-core/git-sh-setup: uname: not found
Thanks for reporting. The issue is related to the expansion of PATH environment variable by the plugin. We will have the fix for this issue soon. For now, if you go into Preferences > C/C++ > Build > Environment and edit PATH environment variable value, you will see that it ends with ":$PATH" string. You can replace this with ":/usr/local/bin:/usr/bin:/bin" (or whatever your system PATH string is). Then the build should succeed.
(internal reference: IEP-74)
Re: Eclipse plugin for ESP-IDF CMake based projects (4.x and above)
PaulVdBergh wrote: ↑Tue Sep 17, 2019 10:39 pm..
How can I use the esp-idf/requirements.txt file to make it usefull ?
..
Thanks for your appreciated response,
Paul
Edit:Code: Select all
paulvdbergh@debian-10:~$ python3.7 --version Python 3.7.4 paulvdbergh@debian-10:~$
Hi Paul,
u're welcome
to your question
usually the idf.py / IDF / esptool is making this call byself for each requirement
also the install process is now automatically more the more, but for your info:
example:
Code: Select all
pip install --user -r requirements.txt
espressifer's work hard for do for us the most steps more the more automatically processed
you find a text passage of this customized by hand doings in an other help, example here
we have more different requirements in the IDF - it is depending which and what will/is/must be installed.
it is usually an automatically process.
can be, that the missing (..:$ENV{PATH}:..) Var like ESP_igrr mentioned is the basicly reason for it,
and some tools was not found
you can check the log for more example ( taken from your hello_world_example )
/home/paulvdbergh/eclipse-workspace/Hello_world/build/CMakeFiles/CMakeOutput.log
hope this helps for info and describe what requirements.txt do/for what it is.
best wishes
rudi
-------------------------------------
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪
- PaulVdBergh
- Posts: 58
- Joined: Fri Feb 23, 2018 4:45 pm
- Location: Brasschaat, Belgium
Re: Eclipse plugin for ESP-IDF CMake based projects (4.x and above)
Hi ESP_igrr,
Your workaround :
did the job.
Thanks. Any idea when this bug will be fixed?
Kind regards,
Paul
Your workaround :
Code: Select all
For now, if you go into Preferences > C/C++ > Build > Environment and edit PATH environment variable value, you will see that it ends with ":$PATH" string. You can replace this with ":/usr/local/bin:/usr/bin:/bin" (or whatever your system PATH string is). Then the build should succeed.
Thanks. Any idea when this bug will be fixed?
Kind regards,
Paul
Re: Eclipse plugin for ESP-IDF CMake based projects (4.x and above)
HI All,
After a long time as a reader only, this post invite me to write my first port.
Thank you for the plugin information, however I'm facing some issues, I follow all steps and I'm able to compile and flash from Eclipse on Windows 10.
However I did skip the "Esspressif IDF Tools Manager -> Install Tools" because it raise the follow error:
My first action to verify my python installation and Windows Registry configuration. Everything is fine as you can also see in the "ESP-IDF Command Prompt" bellow:
I'm not a Java expert, however I try to debug the code using the test methods introduced by developers then I find the follow error:
So, anyone has any suggestion to handle that issues?
Any help and thougths are very welcome.
Sorry for long post and thank you advance.
BR,
Carlos
After a long time as a reader only, this post invite me to write my first port.
Thank you for the plugin information, however I'm facing some issues, I follow all steps and I'm able to compile and flash from Eclipse on Windows 10.
However I did skip the "Esspressif IDF Tools Manager -> Install Tools" because it raise the follow error:
Code: Select all
!ENTRY com.espressif.idf.core 1 0 2019-09-19 22:07:03.003
!MESSAGE Command id:com.espressif.idf.ui.command.install
!ENTRY com.espressif.idf.core 1 0 2019-09-19 22:07:03.004
!MESSAGE
!ENTRY org.eclipse.e4.ui.workbench 4 0 2019-09-19 22:07:03.005
!MESSAGE Command 'com.espressif.idf.ui.command.install' failed
!STACK 0
org.eclipse.core.commands.ExecutionException: No Python installations found in the system.
at com.espressif.idf.ui.update.AbstractToolsHandler.execute(AbstractToolsHandler.java:71)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:283)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:95)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:318)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:252)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:173)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:156)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:498)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:438)
at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449)
at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:475)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4173)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3986)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3585)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1160)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1049)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:633)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:557)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:150)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:660)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597)
at org.eclipse.equinox.launcher.Main.run(Main.java:1468)
Code: Select all
!ENTRY com.espressif.idf.core 1 0 2019-09-19 22:07:03.003
!MESSAGE Command id:com.espressif.idf.ui.command.install
!ENTRY com.espressif.idf.core 1 0 2019-09-19 22:07:03.004
!MESSAGE
!ENTRY org.eclipse.e4.ui.workbench 4 0 2019-09-19 22:07:03.005
!MESSAGE Command 'com.espressif.idf.ui.command.install' failed
!STACK 0
org.eclipse.core.commands.ExecutionException: No Python installations found in the system.
at com.espressif.idf.ui.update.AbstractToolsHandler.execute(AbstractToolsHandler.java:71)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:283)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:95)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:318)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:252)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:173)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:156)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:498)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:438)
at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449)
at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:475)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4173)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3986)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3585)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1160)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1049)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:633)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:557)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:150)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:660)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597)
at org.eclipse.equinox.launcher.Main.run(Main.java:1468)
Code: Select all
java.lang.NoSuchMethodException: java.util.prefs.WindowsPreferences.WindowsRegOpenKey(int, [B, int)
at java.base/java.lang.Class.getDeclaredMethod(Class.java:2476)
at WinRegistry.<clinit>(WinRegistry.java:50)
at PyWinRegistryReader.getPythonVersions(PyWinRegistryReader.java:49)
at PyWinRegistryReader.main(PyWinRegistryReader.java:97)
Any help and thougths are very welcome.
Sorry for long post and thank you advance.
BR,
Carlos
Re: Eclipse plugin for ESP-IDF CMake based projects (4.x and above)
Hi Paul,
The fix has been already pushed to Github in https://github.com/espressif/idf-eclips ... bf710380b3, and the release site will be updated within the next couple of days.
-
- Posts: 188
- Joined: Wed Jul 17, 2019 5:26 pm
Re: Eclipse plugin for ESP-IDF CMake based projects (4.x and above)
Hi Carlos,xSampaio wrote: ↑Fri Sep 20, 2019 1:53 amCode: Select all
java.lang.NoSuchMethodException: java.util.prefs.WindowsPreferences.WindowsRegOpenKey(int, [B, int) at java.base/java.lang.Class.getDeclaredMethod(Class.java:2476) at WinRegistry.<clinit>(WinRegistry.java:50) at PyWinRegistryReader.getPythonVersions(PyWinRegistryReader.java:49) at PyWinRegistryReader.main(PyWinRegistryReader.java:97)
We are sorry for that, could you please provide the error log from the Eclipse to analye the issue. You can find the instructions here https://github.com/espressif/idf-eclips ... #error-log
Best Regards,
Kondal
Who is online
Users browsing this forum: No registered users and 51 guests