espressif / idf-eclipse-plugin Goto Github PK

In the SDK configurator when in the FreeRTOS selection the scroll bar is not responding making it impossible to reach the lower parts of the configurator.
A related feature request:
Can a horizontal scroll bar be used when the window is not entirely visible?

Re-installed eclipse, ESP-IDF & tools, twice to make sure I didn't miss a step.
Tried to build "hello_world"
Got unresolved inclusions on:
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "esp_system.h"
#include "esp_spi_flash.h"

Saw some potential solutions to include certain directories in Project>Properties>C/C++ General> Paths and Symbols, but this choice doesn't exist in my project.
Another potential solution was right-click project and go to Properties>C/C++ Build but that doesn't exist either.

Others have fixed this by adding:
${IDF_PATH}/components/esp32/include
${IDF_PATH}/components/newlib/include
${IDF_PATH}/components/freertos/include
${IDF_PATH}/components/nvs_flash/include
${IDF_PATH}/components/driver/include
${IDF_PATH}/components/log/include
But WHERE do I add this in my setup?

My configuration is:
Ubuntu 19.10 in VMware Workstation 15 VM guest on Windows 10 Host
Eclipse 2019-09 R (4.13.0)
ESP-IDF v4.0-beta2

I have installed the plugin through the automatic procedure.
While I can successfully build and flash a program by command line, I get the following error in Eclipse:

Errors occurred during the build.
Errors running builder 'CDT Core Builder' on project 'hello_world'.
Building hello_world
Cannot run program "/home/maurizio/Development/esp/esp-idf/tools/cmake" (in directory "/home/maurizio/Development/eclipse-workspace/hello_world/build"): error=13, Permission denied
Building hello_world
Cannot run program "/home/maurizio/Development/esp/esp-idf/tools/cmake" (in directory "/home/maurizio/Development/eclipse-workspace/hello_world/build"): error=13, Permission denied

I believe to have carefully followed instructions while setting up the environment and the plugin.
It looks like the project is not recognized as an Espressif IDF Project, same thing If I manually configure parameters.
Environment variables (both in system and in Eclipse) are OK as stated on instructions.
Some parameter fields in Eclipsed are not automatically configured by the plugin.
Indexer doesn't recognize include files (even when, if manually configured, Eclipse successfully compiles the project with no errors)

When double clicking on the sdkconfig, it will prompt a dialog stating "Starting JSON Configuration Server" and the it will failed with a message on a new tab:

"Error retrieving output from the json configuration server, please check the console"

I have been check issue #4 but no result. I have slightly anotger messages in Console.
So I updated back to latest "Espressif IDF Plugins for Eclipse" v1.0.0.201911081309 after trying local build from #4 issue.

Im trying with hello world example project. I manage to build it and flash to ESP32, checked response from COM port. But Can not open sdkconfig tool:

ErrorLog looks clear, I only see problem in Console:

  File "C:\esp\esp-idf-v4.1-dev\tools\kconfig_new\confgen.py", line 94, in replace
    with open(sdkconfig_in, 'r') as f_in, open(sdkconfig_out, 'w') as f_out:
PermissionError: [Errno 13] Permission denied: 'C:\\Users\\E_CAD\\TEMP\\tmpoq0ztips'

ErrorLog.log
Console.txt

It is not default TEMP location, was trying different paths, not helps.
Folder properties in explorer looks ok:

PS: I experienced a python issue during tutorial installation on clear machine
https://github.com/espressif/idf-eclipse-plugin/blob/master/README.md
Python from
C:\Users\E_CAD.espressif\python_env
don't see pip installed, so everything I was done - just remove
C:\Users\E_CAD.espressif\python_env
directory and set IDF_PYTHON_ENV_PATH to system preinstalled python path
C:\Program Files\Python38
After that Eclipse ask to manually do
C:\\Program Files\\Python38\\python.exe -m pip install -r C:\\esp\\esp-idf-v4.1-dev\\requirements.txt
And after that compillation and flashing goes fine.

My system PATH variable from CMD:

C:\Users\E_CAD>PATH
PATH=C:\Program Files\Python38;C:\Program Files\Python38\Scripts;C:\Windows\syst
em32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v
1.0\;C:\Program Files\Git\cmd;C:\Program Files\Java\jdk-13.0.1\bin

IDF_PATH:
C:\esp\esp-idf-v4.1-dev
IDF_PYTHON_ENV_PATH:
C:\Program Files\Python38
OPENOCD_SCRIPTS:
C:\Users\E_CAD\.espressif\tools\openocd-esp32\v0.10.0-esp32-20190708\openocd-esp32\share\openocd\scripts
PATH (Eclipse enviroment):
C:\Users\E_CAD\.espressif\tools\xtensa-esp32-elf\esp32-2019r1-8.2.0\xtensa-esp32-elf\bin;C:\Users\E_CAD\.espressif\tools\esp32ulp-elf\2.28.51.20170517\esp32ulp-elf-binutils\bin;C:\Users\E_CAD\.espressif\tools\cmake\3.13.4\bin;C:\Users\E_CAD\.espressif\tools\openocd-esp32\v0.10.0-esp32-20190708\openocd-esp32\bin;C:\Users\E_CAD\.espressif\tools\mconf\v4.6.0.0-idf-20190628\;C:\Users\E_CAD\.espressif\tools\ninja\1.9.0\;C:\Users\E_CAD\.espressif\tools\idf-exe\1.0.1\;C:\Users\E_CAD\.espressif\tools\ccache\3.7\;C:\esp\esp-idf-v4.1-dev\tools;C:/Program Files/Java/jdk-13.0.1/bin/server;C:/Program Files/Java/jdk-13.0.1/bin;C:\Program Files\Python38;C:\Program Files\Python38\Scripts;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Git\cmd;C:\Program Files\Java\jdk-13.0.1\bin;C:\Users\E_CAD\eclipse\cpp-latest-released\eclipse

I also done everything similar on ubuntu - and there sdkconfig opens fine.

Environment Information:
Configuration.txt

ESP-IDF Tools Information:
ESP-IDF Tools.txt

If i select list installed tools the window "Install tools..." opens instead

I installed “esp-idf-tools-setup-2.1.exe" "eclipse CDT" "IDF Plugins" according to the steps, and after completion, the Unresolved inclusion appeared: < XXX. H >

Hi the community!

I'm using Eclipse 2018-12 CDT.
I'm trying to run the HelloWorld Exemple. So far I was able to do all steps in https://github.com/espressif/idf-eclipse-plugin/blob/master/README.md#ConfigureLaunchTarget until the Configuration Launch Target step. The instrutions talk about a third dropdown which is this one I guess:

Unfortunately I don't have (or I don't see) this dropdown. Here is what I have:

I'm able to get this, which is, I guess, equivalent:

But then I'm expecting to set the Serial Port as shown in the instructions:

... but this is what I have instead:

So, is there a problem with the instructions or am I doing something wrong?

Thanks in advance.

I'm new to esp-idf development (only ESP32 Arduino, even if I used Eclipse for STM32 and others)

I'm planning to use esp-idf 3.3 LTS, as it seems the best choice for long term, so I downloaded the ZIP file with all the submodules and expanded into my work directory

I followed the instructions here https://github.com/espressif/idf-eclipse-plugin/blob/master/README.md. I'm on Windows 10, and with Python 3.7.4

I installed the plugins per instructions, following "Installing IDF Plugins using update site url". When I tried to follow "Installing ESP-IDF Tools", I got an error because the 3.3 release is missing idf_tools.py (and so does 3.1.6, btw). I copied a few missing files from the latest github version, under tools. When re-executing the "install tools", I got an error due to a missing Python library. I installed it with "pip install subprocess.run", relaunched again.

This time it downloaded the tools properly, but then the next 2 steps failed again with an error...

At this point I'm lost... I can see that the tools have been installed (using the "List installed tools" option), but I don't know if the environment has been set properly or not

What am I missing?

Executing C:\Program Files\Python37\python.exe C:\ESP32\esp-idf-v3.3\tools\idf_tools.py install-python-env
Traceback (most recent call last):
File "C:\ESP32\esp-idf-v3.3\tools\idf_tools.py", line 1317, in
main(sys.argv[1:])
File "C:\ESP32\esp-idf-v3.3\tools\idf_tools.py", line 1313, in main
action_func(args)
File "C:\ESP32\esp-idf-v3.3\tools\idf_tools.py", line 1112, in action_install_python_env
idf_python_env_path, , virtualenv_python = get_python_env_path()
File "C:\ESP32\esp-idf-v3.3\tools\idf_tools.py", line 813, in get_python_env_path
idf_version_str = subprocess.check_output(['git', '-C', global_idf_path, 'describe', '--tags'], cwd=global_idf_path, env=os.environ).decode()
File "C:\Program Files\Python37\lib\subprocess.py", line 395, in check_output
**kwargs).stdout
File "C:\Program Files\Python37\lib\site-packages\run_init.py", line 145, in new
process = cls.create_process(command, stdin, cwd=cwd, env=env, shell=shell)
File "C:\Program Files\Python37\lib\site-packages\run_init_.py", line 121, in create_process
shlex.split(command),
File "C:\Program Files\Python37\lib\shlex.py", line 305, in split
return list(lex)
File "C:\Program Files\Python37\lib\shlex.py", line 295, in next
token = self.get_token()
File "C:\Program Files\Python37\lib\shlex.py", line 105, in get_token
raw = self.read_token()
File "C:\Program Files\Python37\lib\shlex.py", line 136, in read_token
nextchar = self.instream.read(1)
AttributeError: 'list' object has no attribute 'read'

Executing C:\Program Files\Python37\python.exe C:\ESP32\esp-idf-v3.3\tools\idf_tools.py export --format=key-value
Traceback (most recent call last):
File "C:\ESP32\esp-idf-v3.3\tools\idf_tools.py", line 1317, in
main(sys.argv[1:])
File "C:\ESP32\esp-idf-v3.3\tools\idf_tools.py", line 1313, in main
action_func(args)
File "C:\ESP32\esp-idf-v3.3\tools\idf_tools.py", line 953, in action_export
idf_python_env_path, idf_python_export_path, virtualenv_python = get_python_env_path()
File "C:\ESP32\esp-idf-v3.3\tools\idf_tools.py", line 813, in get_python_env_path
idf_version_str = subprocess.check_output(['git', '-C', global_idf_path, 'describe', '--tags'], cwd=global_idf_path, env=os.environ).decode()
File "C:\Program Files\Python37\lib\subprocess.py", line 395, in check_output
**kwargs).stdout
File "C:\Program Files\Python37\lib\site-packages\run_init_.py", line 145, in new
process = cls.create_process(command, stdin, cwd=cwd, env=env, shell=shell)
File "C:\Program Files\Python37\lib\site-packages\run_init_.py", line 121, in create_process
shlex.split(command),
File "C:\Program Files\Python37\lib\shlex.py", line 305, in split
return list(lex)
File "C:\Program Files\Python37\lib\shlex.py", line 295, in next
token = self.get_token()
File "C:\Program Files\Python37\lib\shlex.py", line 105, in get_token
raw = self.read_token()
File "C:\Program Files\Python37\lib\shlex.py", line 136, in read_token
nextchar = self.instream.read(1)
AttributeError: 'list' object has no attribute 'read'

Hi,

I am following this documentation to get started on ESP32 using Eclipse, trying to replicate the steps on Windows 10.
I have successfully configured the target, but while compiling the project, the build console shows "No Toolchain found for Target esp32", unlike has been documented.
Kindly help!

After importing an existing project, some files were truncated (content lost, 0 byte file size). These are:
partitions.csv, sdkconfig, CMakeList.txt, ...

I have setup with the plugin. Everything compiles, I can check declaration of ESP functions but not able to go to function definitions. Is there any easy way to configure Eclipse to show function definition so that debugging is easy

I got an infinite loop while trying to build with eclipse. On console everything works as expected.

cmake --build . -- -v
CMake Error: The current CMakeCache.txt directory /home/sven/workspace/Water Me/build/CMakeCache.txt is different than the directory /home/sven/workspace/esp/water-me/build where CMakeCache.txt was created. This may result in binaries being created in the wrong place. If you are not sure, reedit the CMakeCache.txt
[0/1] /usr/bin/cmake -H/home/sven/workspace/esp/water-me -B/home/sven/workspace/esp/water-me/build
-- Component directory /home/sven/workspace/esp/esp-idf/components/aws_iot does not contain a CMakeLists.txt file. No component will be added
-- Component directory /home/sven/workspace/esp/esp-idf/components/micro-ecc does not contain a CMakeLists.txt file. No component will be added
/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: basename: 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: 332: /usr/lib/git-core/git-sh-setup: uname: not found
-- Project version: 684fab7-dirty
-- Building ESP-IDF components for target esp32
-- Adding linker script /home/sven/workspace/esp/water-me/build/esp-idf/esp32/esp32_out.ld
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp32/ld/esp32.project.ld.in
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp32/ld/esp32.peripherals.ld
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp_rom/esp32/ld/esp32.rom.ld
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp_rom/esp32/ld/esp32.rom.libgcc.ld
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp_rom/esp32/ld/esp32.rom.syscalls.ld
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp_rom/esp32/ld/esp32.rom.newlib-data.ld
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp_rom/esp32/ld/esp32.rom.newlib-funcs.ld
-- Components: app_trace app_update asio bootloader bootloader_support bt coap console cxx driver efuse esp-tls esp32 esp32-wifi-manager esp_adc_cal esp_common esp_eth esp_event esp_gdbstub esp_http_client esp_http_server esp_https_ota esp_https_server esp_local_ctrl esp_ringbuf esp_rom esp_websocket_client esp_wifi espcoredump esptool_py expat fatfs freemodbus freertos heap idf_test jsmn json libsodium log lwip main mbedtls mdns mkspiffs mqtt newlib nghttp nvs_flash openssl partition_table protobuf-c protocomm pthread sdmmc soc spi_flash spidriver spiffs spiffs_image tcp_transport tcpip_adapter tft ulp unity vfs wear_levelling wifi_provisioning wpa_supplicant xtensa
-- Component paths: /home/sven/workspace/esp/esp-idf/components/app_trace /home/sven/workspace/esp/esp-idf/components/app_update /home/sven/workspace/esp/esp-idf/components/asio /home/sven/workspace/esp/esp-idf/components/bootloader /home/sven/workspace/esp/esp-idf/components/bootloader_support /home/sven/workspace/esp/esp-idf/components/bt /home/sven/workspace/esp/esp-idf/components/coap /home/sven/workspace/esp/esp-idf/components/console /home/sven/workspace/esp/esp-idf/components/cxx /home/sven/workspace/esp/esp-idf/components/driver /home/sven/workspace/esp/esp-idf/components/efuse /home/sven/workspace/esp/esp-idf/components/esp-tls /home/sven/workspace/esp/esp-idf/components/esp32 /home/sven/workspace/esp/water-me/components/esp32-wifi-manager /home/sven/workspace/esp/esp-idf/components/esp_adc_cal /home/sven/workspace/esp/esp-idf/components/esp_common /home/sven/workspace/esp/esp-idf/components/esp_eth /home/sven/workspace/esp/esp-idf/components/esp_event /home/sven/workspace/esp/esp-idf/components/esp_gdbstub /home/sven/workspace/esp/esp-idf/components/esp_http_client /home/sven/workspace/esp/esp-idf/components/esp_http_server /home/sven/workspace/esp/esp-idf/components/esp_https_ota /home/sven/workspace/esp/esp-idf/components/esp_https_server /home/sven/workspace/esp/esp-idf/components/esp_local_ctrl /home/sven/workspace/esp/esp-idf/components/esp_ringbuf /home/sven/workspace/esp/esp-idf/components/esp_rom /home/sven/workspace/esp/esp-idf/components/esp_websocket_client /home/sven/workspace/esp/esp-idf/components/esp_wifi /home/sven/workspace/esp/esp-idf/components/espcoredump /home/sven/workspace/esp/esp-idf/components/esptool_py /home/sven/workspace/esp/esp-idf/components/expat /home/sven/workspace/esp/esp-idf/components/fatfs /home/sven/workspace/esp/esp-idf/components/freemodbus /home/sven/workspace/esp/esp-idf/components/freertos /home/sven/workspace/esp/esp-idf/components/heap /home/sven/workspace/esp/esp-idf/components/idf_test /home/sven/workspace/esp/esp-idf/components/jsmn /home/sven/workspace/esp/esp-idf/components/json /home/sven/workspace/esp/esp-idf/components/libsodium /home/sven/workspace/esp/esp-idf/components/log /home/sven/workspace/esp/esp-idf/components/lwip /home/sven/workspace/esp/water-me/main /home/sven/workspace/esp/esp-idf/components/mbedtls /home/sven/workspace/esp/esp-idf/components/mdns /home/sven/workspace/esp/water-me/components/indirectBuild/ESP32_TFT_library/components/mkspiffs /home/sven/workspace/esp/esp-idf/components/mqtt /home/sven/workspace/esp/esp-idf/components/newlib /home/sven/workspace/esp/esp-idf/components/nghttp /home/sven/workspace/esp/esp-idf/components/nvs_flash /home/sven/workspace/esp/esp-idf/components/openssl /home/sven/workspace/esp/esp-idf/components/partition_table /home/sven/workspace/esp/esp-idf/components/protobuf-c /home/sven/workspace/esp/esp-idf/components/protocomm /home/sven/workspace/esp/esp-idf/components/pthread /home/sven/workspace/esp/esp-idf/components/sdmmc /home/sven/workspace/esp/esp-idf/components/soc /home/sven/workspace/esp/esp-idf/components/spi_flash /home/sven/workspace/esp/water-me/components/indirectBuild/ESP32_TFT_library/components/spidriver /home/sven/workspace/esp/water-me/components/indirectBuild/ESP32_TFT_library/components/spiffs /home/sven/workspace/esp/water-me/components/indirectBuild/ESP32_TFT_library/components/spiffs_image /home/sven/workspace/esp/esp-idf/components/tcp_transport /home/sven/workspace/esp/esp-idf/components/tcpip_adapter /home/sven/workspace/esp/water-me/components/indirectBuild/ESP32_TFT_library/components/tft /home/sven/workspace/esp/esp-idf/components/ulp /home/sven/workspace/esp/esp-idf/components/unity /home/sven/workspace/esp/esp-idf/components/vfs /home/sven/workspace/esp/esp-idf/components/wear_levelling /home/sven/workspace/esp/esp-idf/components/wifi_provisioning /home/sven/workspace/esp/esp-idf/components/wpa_supplicant /home/sven/workspace/esp/esp-idf/components/xtensa
-- Configuring done
-- Generating done
-- Build files have been written to: /home/sven/workspace/esp/water-me/build
[0/1] /usr/bin/cmake -H/home/sven/workspace/esp/water-me -B/home/sven/workspace/esp/water-me/build
-- Component directory /home/sven/workspace/esp/esp-idf/components/aws_iot does not contain a CMakeLists.txt file. No component will be added
-- Component directory /home/sven/workspace/esp/esp-idf/components/micro-ecc does not contain a CMakeLists.txt file. No component will be added
/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: basename: 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: 332: /usr/lib/git-core/git-sh-setup: uname: not found
-- Project version: 684fab7-dirty
-- Building ESP-IDF components for target esp32
-- Adding linker script /home/sven/workspace/esp/water-me/build/esp-idf/esp32/esp32_out.ld
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp32/ld/esp32.project.ld.in
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp32/ld/esp32.peripherals.ld
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp_rom/esp32/ld/esp32.rom.ld
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp_rom/esp32/ld/esp32.rom.libgcc.ld
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp_rom/esp32/ld/esp32.rom.syscalls.ld
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp_rom/esp32/ld/esp32.rom.newlib-data.ld
-- Adding linker script /home/sven/workspace/esp/esp-idf/components/esp_rom/esp32/ld/esp32.rom.newlib-funcs.ld
-- Components: app_trace app_update asio bootloader bootloader_support bt coap console cxx driver efuse esp-tls esp32 esp32-wifi-manager esp_adc_cal esp_common esp_eth esp_event esp_gdbstub esp_http_client esp_http_server esp_https_ota esp_https_server esp_local_ctrl esp_ringbuf esp_rom esp_websocket_client esp_wifi espcoredump esptool_py expat fatfs freemodbus freertos heap idf_test jsmn json libsodium log lwip main mbedtls mdns mkspiffs mqtt newlib nghttp nvs_flash openssl partition_table protobuf-c protocomm pthread sdmmc soc spi_flash spidriver spiffs spiffs_image tcp_transport tcpip_adapter tft ulp unity vfs wear_levelling wifi_provisioning wpa_supplicant xtensa
-- Component paths: /home/sven/workspace/esp/esp-idf/components/app_trace /home/sven/workspace/esp/esp-idf/components/app_update /home/sven/workspace/esp/esp-idf/components/asio /home/sven/workspace/esp/esp-idf/components/bootloader /home/sven/workspace/esp/esp-idf/components/bootloader_support /home/sven/workspace/esp/esp-idf/components/bt /home/sven/workspace/esp/esp-idf/components/coap /home/sven/workspace/esp/esp-idf/components/console /home/sven/workspace/esp/esp-idf/components/cxx /home/sven/workspace/esp/esp-idf/components/driver /home/sven/workspace/esp/esp-idf/components/efuse /home/sven/workspace/esp/esp-idf/components/esp-tls /home/sven/workspace/esp/esp-idf/components/esp32 /home/sven/workspace/esp/water-me/components/esp32-wifi-manager /home/sven/workspace/esp/esp-idf/components/esp_adc_cal /home/sven/workspace/esp/esp-idf/components/esp_common /home/sven/workspace/esp/esp-idf/components/esp_eth /home/sven/workspace/esp/esp-idf/components/esp_event /home/sven/workspace/esp/esp-idf/components/esp_gdbstub /home/sven/workspace/esp/esp-idf/components/esp_http_client /home/sven/workspace/esp/esp-idf/components/esp_http_server /home/sven/workspace/esp/esp-idf/components/esp_https_ota /home/sven/workspace/esp/esp-idf/components/esp_https_server /home/sven/workspace/esp/esp-idf/components/esp_local_ctrl /home/sven/workspace/esp/esp-idf/components/esp_ringbuf /home/sven/workspace/esp/esp-idf/components/esp_rom /home/sven/workspace/esp/esp-idf/components/esp_websocket_client /home/sven/workspace/esp/esp-idf/components/esp_wifi /home/sven/workspace/esp/esp-idf/components/espcoredump /home/sven/workspace/esp/esp-idf/components/esptool_py /home/sven/workspace/esp/esp-idf/components/expat /home/sven/workspace/esp/esp-idf/components/fatfs /home/sven/workspace/esp/esp-idf/components/freemodbus /home/sven/workspace/esp/esp-idf/components/freertos /home/sven/workspace/esp/esp-idf/components/heap /home/sven/workspace/esp/esp-idf/components/idf_test /home/sven/workspace/esp/esp-idf/components/jsmn /home/sven/workspace/esp/esp-idf/components/json /home/sven/workspace/esp/esp-idf/components/libsodium /home/sven/workspace/esp/esp-idf/components/log /home/sven/workspace/esp/esp-idf/components/lwip /home/sven/workspace/esp/water-me/main /home/sven/workspace/esp/esp-idf/components/mbedtls /home/sven/workspace/esp/esp-idf/components/mdns /home/sven/workspace/esp/water-me/components/indirectBuild/ESP32_TFT_library/components/mkspiffs /home/sven/workspace/esp/esp-idf/components/mqtt /home/sven/workspace/esp/esp-idf/components/newlib /home/sven/workspace/esp/esp-idf/components/nghttp /home/sven/workspace/esp/esp-idf/components/nvs_flash /home/sven/workspace/esp/esp-idf/components/openssl /home/sven/workspace/esp/esp-idf/components/partition_table /home/sven/workspace/esp/esp-idf/components/protobuf-c /home/sven/workspace/esp/esp-idf/components/protocomm /home/sven/workspace/esp/esp-idf/components/pthread /home/sven/workspace/esp/esp-idf/components/sdmmc /home/sven/workspace/esp/esp-idf/components/soc /home/sven/workspace/esp/esp-idf/components/spi_flash /home/sven/workspace/esp/water-me/components/indirectBuild/ESP32_TFT_library/components/spidriver /home/sven/workspace/esp/water-me/components/indirectBuild/ESP32_TFT_library/components/spiffs /home/sven/workspace/esp/water-me/components/indirectBuild/ESP32_TFT_library/components/spiffs_image /home/sven/workspace/esp/esp-idf/components/tcp_transport /home/sven/workspace/esp/esp-idf/components/tcpip_adapter /home/sven/workspace/esp/water-me/components/indirectBuild/ESP32_TFT_library/components/tft /home/sven/workspace/esp/esp-idf/components/ulp /home/sven/workspace/esp/esp-idf/components/unity /home/sven/workspace/esp/esp-idf/components/vfs /home/sven/workspace/esp/esp-idf/components/wear_levelling /home/sven/workspace/esp/esp-idf/components/wifi_provisioning /home/sven/workspace/esp/esp-idf/components/wpa_supplicant /home/sven/workspace/esp/esp-idf/components/xtensa
-- Configuring done
-- Generating done
-- Build files have been written to: /home/sven/workspace/esp/water-me/build

Hi Community.
Sorry in advance, I don't have a lot of experience in Eclipse and almost none with Espressif.

I'm using Eclipse 2018-12 (4.10.0) build 20181214-0600
I have installed succesfully ESP-IDF 3.3 and the tools with the Tools Installer and was able to open the menuconfig and build the Hello Worl example.

Then I tried to install the pluggin in Eclipse and found that IDF 4.0 (at least) was required. So I have installed 4.0 and the Tools with the Tool Installer again. And I was also able to open the menuconfig and build the Hello Worl example in IDF 4.0.

Unfortunately when I try to install the pluggin in Eclipse, when it tries to install the ESP-IDF Tools (according to https://github.com/espressif/idf-eclipse-plugin/blob/master/README.md, section "Installing ESP-IDF Tools"), it fails. And this is what the Eclipse Console shows:

Executing C:\Users\bbeliveau\AppData\Local\Programs\Python\Python37-32\python.exe C:\Users\bbeliveau\Documents\Espressif\esp-idf_3_3\tools\idf_tools.py export --format=key-value
C:\Users\bbeliveau\AppData\Local\Programs\Python\Python37-32\python.exe: can't open file 'C:\Users\bbeliveau\Documents\Espressif\esp-idf_3_3\tools\idf_tools.py': [Errno 2] No such file or directory

...where it looks for idf_tools.py from my old ESP-IDF 3.3 folder.

So where I can change this to make sure it is looking for my 4.0 folder instead?

Thanks for your help!

Hello all,
I clean install this plugin and all requirements (Eclipse IDE version: 2019-12).
I start with New -> Espressif IDF Project.
I choose for example Hello World.

Problem is that projects in explorer not have sdkconfig and here is only what you see in the picture.

**Environment Information
eclipseEnvironmentInformation.txt

From this page here:
https://github.com/espressif/idf-eclipse-plugin/releases

The following on that page takes you to a 403 Forbidden page

Installing IDF Plugins using update site URL:
https://dl.espressif.com/dl/idf-eclipse-plugin/updates/latest/

I followed step by step the instruction.
Installed the plugin using URL method.
Then I go to:
Help > Espressif IDF Tools Manager > Install Tools
and after pushing install nothing happens.
Directory selection dialog doesn't appear.

I am using:
Eclipse - Version: 2019-09 R (4.13.0), Build id: 20190917-1200
Java - Java SE Development Kit 13

Even with the latest code, I'm getting an install tools failure that leaves only the IDF_PATH configured in eclipse (using 2019-12M1 but I do not believe that matters, I was using 2019-09 before).

What I realized is that 'git' is not found on the Windows PATH, so get_version() and such fail with file not found.

I added the git dir ("C:\Program Files\Git\cmd" on my system) to my Windows PATH variable and now install tools succeeds - and now I get to use an IDE, I sure missed that.

So either this needs to be documented in the release notes/FAQ (I looked but perhaps missed it) or a solution needs to be found in the plugin.

Next thing, soon enough, will be getting OpenOCD going, but that's far too complicated. You know how happy I'll be when that works turnkey...

Hi, my name is Alejandro,

I have done the tutorial "Espressif IDF Eclipse Plugins". but when I get to the step "Installing ESP-IDF Tools", I encounter the following error in the Eclipse console:

Installing tools...
This can take a while. Please be patient.
Executing D:\Users\Alejandro\AppData\Local\Programs\Python\Python37-32\python.exe C:\Users\Alejandro\Desktop\esp-idf\tools\idf_tools.py install all
D:\Users\Alejandro\AppData\Local\Programs\Python\Python37-32\python.exe: can't open file 'C:\Users\Alejandro\Desktop\esp-idf\tools\idf_tools.py': [Errno 2] No such file or directory

Executing D:\Users\Alejandro\AppData\Local\Programs\Python\Python37-32\python.exe C:\Users\Alejandro\Desktop\esp-idf\tools\idf_tools.py install-python-env
D:\Users\Alejandro\AppData\Local\Programs\Python\Python37-32\python.exe: can't open file 'C:\Users\Alejandro\Desktop\esp-idf\tools\idf_tools.py': [Errno 2] No such file or directory

Executing D:\Users\Alejandro\AppData\Local\Programs\Python\Python37-32\python.exe C:\Users\Alejandro\Desktop\esp-idf\tools\idf_tools.py export --format=key-value
D:\Users\Alejandro\AppData\Local\Programs\Python\Python37-32\python.exe: can't open file 'C:\Users\Alejandro\Desktop\esp-idf\tools\idf_tools.py': [Errno 2] No such file or directory

could someone help me solve the problem?

Thanks.

The following error pops up when I am trying to build the "blink" project.

Note: I have been following "https://github.com/espressif/idf-eclipse-plugin/blob/master/README.md" to set up my ESP-32 on Eclipse. I am stuck in the Compiling stage of it. I have also done the necessary changes and set necessary locations in the "blink' property like PATH, IDF_PATH, V etc.

Console Output:

make all
including /c/Users/40007382/Desktop/esp-idf/components/app_update/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/bootloader/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/bootloader_support/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/coap/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/efuse/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/esp32/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/esptool_py/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/mbedtls/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/nghttp/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/partition_table/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/ulp/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/unity/Makefile.projbuild...
Toolchain path: /opt/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc
Toolchain version: crosstool-ng-1.22.0-80-g6c4433a5
Compiler version: 5.2.0
PROJECT_PATH= COMPONENT_DIRS= /usr/bin/make -C /c/Users/40007382/Desktop/esp-idf/components/bootloader/subproject V=1 BUILD_DIR_BASE=/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader TEST_COMPONENTS= TESTS_ALL= EXCLUDE_COMPONENTS= /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/bootloader.bin
make[1]: Entering directory '/c/Users/40007382/Desktop/esp-idf/components/bootloader/subproject'
including /c/Users/40007382/Desktop/esp-idf/components/esptool_py/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/bootloader_support/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/bootloader/subproject/main/Makefile.projbuild...
including /c/Users/40007382/Desktop/esp-idf/components/efuse/Makefile.projbuild...
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/bootloader_support -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/bootloader_support/component.mk COMPONENT_NAME=bootloader_support build
make[2]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/bootloader_support'
make[2]: Nothing to be done for 'build'.
make[2]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/bootloader_support'
Target 'component-bootloader_support-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/bootloader_support/libbootloader_support.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/log -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/log/component.mk COMPONENT_NAME=log build
make[2]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/log'
make[2]: Nothing to be done for 'build'.
make[2]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/log'
Target 'component-log-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/log/liblog.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/spi_flash -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/spi_flash/component.mk COMPONENT_NAME=spi_flash build
make[2]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/spi_flash'
make[2]: Nothing to be done for 'build'.
make[2]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/spi_flash'
Target 'component-spi_flash-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/spi_flash/libspi_flash.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/micro-ecc -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/micro-ecc/component.mk COMPONENT_NAME=micro-ecc build
make[2]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/micro-ecc'
make[2]: Nothing to be done for 'build'.
make[2]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/micro-ecc'
Target 'component-micro-ecc-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/micro-ecc/libmicro-ecc.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/soc -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/soc/component.mk COMPONENT_NAME=soc build
make[2]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/soc'
make[2]: Nothing to be done for 'build'.
make[2]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/soc'
Target 'component-soc-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/soc/libsoc.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/main -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/bootloader/subproject/main/component.mk COMPONENT_NAME=main build
make[2]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/main'
make[2]: Nothing to be done for 'build'.
make[2]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/main'
Target 'component-main-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/main/libmain.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/efuse -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/efuse/component.mk COMPONENT_NAME=efuse build
make[2]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/efuse'
make[2]: Nothing to be done for 'build'.
make[2]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/efuse'
Target 'component-efuse-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/efuse/libefuse.a'
make[1]: Leaving directory '/c/Users/40007382/Desktop/esp-idf/components/bootloader/subproject'
python /c/Users/40007382/Desktop/esp-idf/tools/check_python_dependencies.py
Python requirements from C:/Users/40007382/Desktop/esp-idf\requirements.txt are satisfied.

/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/app_trace -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/app_trace/component.mk COMPONENT_NAME=app_trace build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/app_trace'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/app_trace'
Target 'component-app_trace-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/app_trace/libapp_trace.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/app_update -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/app_update/component.mk COMPONENT_NAME=app_update build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/app_update'
Project is not inside a git repository, will not use 'git describe' to determine PROJECT_VER.
App "blink" version: 1
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/app_update'
Target 'component-app_update-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/app_update/libapp_update.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/asio -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/asio/component.mk COMPONENT_NAME=asio build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/asio'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/asio'
Target 'component-asio-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/asio/libasio.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/aws_iot -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/aws_iot/component.mk COMPONENT_NAME=aws_iot build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/aws_iot'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/aws_iot'
Target 'component-aws_iot-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/aws_iot/libaws_iot.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader_support -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/bootloader_support/component.mk COMPONENT_NAME=bootloader_support build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader_support'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader_support'
Target 'component-bootloader_support-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader_support/libbootloader_support.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bt -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/bt/component.mk COMPONENT_NAME=bt build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bt'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bt'
Target 'component-bt-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bt/libbt.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/coap -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/coap/component.mk COMPONENT_NAME=coap build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/coap'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/coap'
Target 'component-coap-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/coap/libcoap.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/console -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/console/component.mk COMPONENT_NAME=console build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/console'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/console'
Target 'component-console-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/console/libconsole.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/cxx -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/cxx/component.mk COMPONENT_NAME=cxx build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/cxx'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/cxx'
Target 'component-cxx-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/cxx/libcxx.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/driver -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/driver/component.mk COMPONENT_NAME=driver build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/driver'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/driver'
Target 'component-driver-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/driver/libdriver.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/efuse -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/efuse/component.mk COMPONENT_NAME=efuse build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/efuse'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/efuse'
Target 'component-efuse-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/efuse/libefuse.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp-tls -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/esp-tls/component.mk COMPONENT_NAME=esp-tls build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp-tls'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp-tls'
Target 'component-esp-tls-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp-tls/libesp-tls.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp32 -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/esp32/component.mk COMPONENT_NAME=esp32 build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp32'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp32'
Target 'component-esp32-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp32/libesp32.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_adc_cal -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/esp_adc_cal/component.mk COMPONENT_NAME=esp_adc_cal build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_adc_cal'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_adc_cal'
Target 'component-esp_adc_cal-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_adc_cal/libesp_adc_cal.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_event -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/esp_event/component.mk COMPONENT_NAME=esp_event build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_event'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_event'
Target 'component-esp_event-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_event/libesp_event.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_http_client -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/esp_http_client/component.mk COMPONENT_NAME=esp_http_client build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_http_client'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_http_client'
Target 'component-esp_http_client-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_http_client/libesp_http_client.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_http_server -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/esp_http_server/component.mk COMPONENT_NAME=esp_http_server build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_http_server'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_http_server'
Target 'component-esp_http_server-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_http_server/libesp_http_server.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_https_ota -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/esp_https_ota/component.mk COMPONENT_NAME=esp_https_ota build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_https_ota'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_https_ota'
Target 'component-esp_https_ota-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_https_ota/libesp_https_ota.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_https_server -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/esp_https_server/component.mk COMPONENT_NAME=esp_https_server build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_https_server'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_https_server'
Target 'component-esp_https_server-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_https_server/libesp_https_server.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_ringbuf -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/esp_ringbuf/component.mk COMPONENT_NAME=esp_ringbuf build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_ringbuf'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_ringbuf'
Target 'component-esp_ringbuf-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/esp_ringbuf/libesp_ringbuf.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/espcoredump -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/espcoredump/component.mk COMPONENT_NAME=espcoredump build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/espcoredump'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/espcoredump'
Target 'component-espcoredump-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/espcoredump/libespcoredump.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/ethernet -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/ethernet/component.mk COMPONENT_NAME=ethernet build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/ethernet'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/ethernet'
Target 'component-ethernet-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/ethernet/libethernet.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/expat -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/expat/component.mk COMPONENT_NAME=expat build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/expat'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/expat'
Target 'component-expat-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/expat/libexpat.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/fatfs -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/fatfs/component.mk COMPONENT_NAME=fatfs build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/fatfs'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/fatfs'
Target 'component-fatfs-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/fatfs/libfatfs.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/freemodbus -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/freemodbus/component.mk COMPONENT_NAME=freemodbus build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/freemodbus'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/freemodbus'
Target 'component-freemodbus-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/freemodbus/libfreemodbus.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/freertos -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/freertos/component.mk COMPONENT_NAME=freertos build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/freertos'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/freertos'
Target 'component-freertos-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/freertos/libfreertos.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/heap -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/heap/component.mk COMPONENT_NAME=heap build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/heap'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/heap'
Target 'component-heap-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/heap/libheap.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/idf_test -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/idf_test/component.mk COMPONENT_NAME=idf_test build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/idf_test'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/idf_test'
Target 'component-idf_test-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/idf_test/libidf_test.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/jsmn -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/jsmn/component.mk COMPONENT_NAME=jsmn build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/jsmn'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/jsmn'
Target 'component-jsmn-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/jsmn/libjsmn.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/json -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/json/component.mk COMPONENT_NAME=json build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/json'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/json'
Target 'component-json-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/json/libjson.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/libsodium -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/libsodium/component.mk COMPONENT_NAME=libsodium build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/libsodium'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/libsodium'
Target 'component-libsodium-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/libsodium/liblibsodium.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/log -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/log/component.mk COMPONENT_NAME=log build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/log'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/log'
Target 'component-log-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/log/liblog.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/lwip -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/lwip/component.mk COMPONENT_NAME=lwip build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/lwip'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/lwip'
Target 'component-lwip-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/lwip/liblwip.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/main -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/eclipse-workspace/attempt/OnOff/main/component.mk COMPONENT_NAME=main build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/main'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/main'
Target 'component-main-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/main/libmain.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/mbedtls -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/mbedtls/component.mk COMPONENT_NAME=mbedtls build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/mbedtls'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/mbedtls'
Target 'component-mbedtls-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/mbedtls/libmbedtls.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/mdns -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/mdns/component.mk COMPONENT_NAME=mdns build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/mdns'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/mdns'
Target 'component-mdns-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/mdns/libmdns.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/micro-ecc -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/micro-ecc/component.mk COMPONENT_NAME=micro-ecc build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/micro-ecc'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/micro-ecc'
Target 'component-micro-ecc-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/micro-ecc/libmicro-ecc.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/mqtt -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/mqtt/component.mk COMPONENT_NAME=mqtt build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/mqtt'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/mqtt'
Target 'component-mqtt-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/mqtt/libmqtt.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/newlib -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/newlib/component.mk COMPONENT_NAME=newlib build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/newlib'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/newlib'
Target 'component-newlib-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/newlib/libnewlib.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/nghttp -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/nghttp/component.mk COMPONENT_NAME=nghttp build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/nghttp'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/nghttp'
Target 'component-nghttp-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/nghttp/libnghttp.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/nvs_flash -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/nvs_flash/component.mk COMPONENT_NAME=nvs_flash build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/nvs_flash'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/nvs_flash'
Target 'component-nvs_flash-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/nvs_flash/libnvs_flash.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/openssl -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/openssl/component.mk COMPONENT_NAME=openssl build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/openssl'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/openssl'
Target 'component-openssl-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/openssl/libopenssl.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/protobuf-c -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/protobuf-c/component.mk COMPONENT_NAME=protobuf-c build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/protobuf-c'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/protobuf-c'
Target 'component-protobuf-c-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/protobuf-c/libprotobuf-c.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/protocomm -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/protocomm/component.mk COMPONENT_NAME=protocomm build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/protocomm'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/protocomm'
Target 'component-protocomm-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/protocomm/libprotocomm.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/pthread -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/pthread/component.mk COMPONENT_NAME=pthread build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/pthread'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/pthread'
Target 'component-pthread-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/pthread/libpthread.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/sdmmc -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/sdmmc/component.mk COMPONENT_NAME=sdmmc build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/sdmmc'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/sdmmc'
Target 'component-sdmmc-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/sdmmc/libsdmmc.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/smartconfig_ack -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/smartconfig_ack/component.mk COMPONENT_NAME=smartconfig_ack build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/smartconfig_ack'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/smartconfig_ack'
Target 'component-smartconfig_ack-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/smartconfig_ack/libsmartconfig_ack.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/soc -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/soc/component.mk COMPONENT_NAME=soc build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/soc'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/soc'
Target 'component-soc-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/soc/libsoc.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/spi_flash -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/spi_flash/component.mk COMPONENT_NAME=spi_flash build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/spi_flash'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/spi_flash'
Target 'component-spi_flash-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/spi_flash/libspi_flash.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/spiffs -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/spiffs/component.mk COMPONENT_NAME=spiffs build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/spiffs'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/spiffs'
Target 'component-spiffs-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/spiffs/libspiffs.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/tcp_transport -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/tcp_transport/component.mk COMPONENT_NAME=tcp_transport build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/tcp_transport'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/tcp_transport'
Target 'component-tcp_transport-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/tcp_transport/libtcp_transport.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/tcpip_adapter -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/tcpip_adapter/component.mk COMPONENT_NAME=tcpip_adapter build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/tcpip_adapter'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/tcpip_adapter'
Target 'component-tcpip_adapter-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/tcpip_adapter/libtcpip_adapter.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/ulp -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/ulp/component.mk COMPONENT_NAME=ulp build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/ulp'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/ulp'
Target 'component-ulp-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/ulp/libulp.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/unity -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/unity/component.mk COMPONENT_NAME=unity build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/unity'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/unity'
Target 'component-unity-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/unity/libunity.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/vfs -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/vfs/component.mk COMPONENT_NAME=vfs build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/vfs'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/vfs'
Target 'component-vfs-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/vfs/libvfs.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/wear_levelling -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/wear_levelling/component.mk COMPONENT_NAME=wear_levelling build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/wear_levelling'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/wear_levelling'
Target 'component-wear_levelling-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/wear_levelling/libwear_levelling.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/wifi_provisioning -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/wifi_provisioning/component.mk COMPONENT_NAME=wifi_provisioning build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/wifi_provisioning'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/wifi_provisioning'
Target 'component-wifi_provisioning-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/wifi_provisioning/libwifi_provisioning.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/wpa_supplicant -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/wpa_supplicant/component.mk COMPONENT_NAME=wpa_supplicant build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/wpa_supplicant'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/wpa_supplicant'
Target 'component-wpa_supplicant-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/wpa_supplicant/libwpa_supplicant.a'
/usr/bin/make -C /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/xtensa-debug-module -f /c/Users/40007382/Desktop/esp-idf/make/component_wrapper.mk COMPONENT_MAKEFILE=/c/Users/40007382/Desktop/esp-idf/components/xtensa-debug-module/component.mk COMPONENT_NAME=xtensa-debug-module build
make[1]: Entering directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/xtensa-debug-module'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/xtensa-debug-module'
Target 'component-xtensa-debug-module-build' responsible for '/c/Users/40007382/eclipse-workspace/attempt/OnOff/build/xtensa-debug-module/libxtensa-debug-module.a'
To flash all build output, run 'make flash' or:
python /c/Users/40007382/Desktop/esp-idf/components/esptool_py/esptool/esptool.py --chip esp32 --port /dev/ttyUSB0 --baud 115200 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x1000 /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/bootloader/bootloader.bin 0x10000 /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/blink.bin 0x8000 /c/Users/40007382/eclipse-workspace/attempt/OnOff/build/partitions_singleapp.bin

Problems Output:

I've installed the plug in into Eclipse and I'm building the project successfully.
But when I try to flash/monitor the program, I have a issue.

Someone can help me to understand this problem, please?

The logs are bellow:

Traceback (most recent call last):
File "/Users/macmini/esp/esp-idf/tools/idf.py", line 1556, in
Adding "flash"'s dependency "all" to list of commands with default set of options.
Executing action: all (aliases: build)
Running ninja in directory /Users/macmini/eclipse-workspace/Wifi_Example/build
Executing "ninja all"...
main()
File "/Users/macmini/esp/esp-idf/tools/idf.py", line 1471, in main
cli(prog_name=PROG)
File "/Users/macmini/.espressif/python_env/idf4.1_py2.7_env/lib/python2.7/site-packages/click/core.py", line 764, in call
return self.main(*args, **kwargs)
File "/Users/macmini/.espressif/python_env/idf4.1_py2.7_env/lib/python2.7/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/Users/macmini/.espressif/python_env/idf4.1_py2.7_env/lib/python2.7/site-packages/click/core.py", line 1164, in invoke
return _process_result(rv)
File "/Users/macmini/.espressif/python_env/idf4.1_py2.7_env/lib/python2.7/site-packages/click/core.py", line 1102, in _process_result
**ctx.params)
File "/Users/macmini/.espressif/python_env/idf4.1_py2.7_env/lib/python2.7/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/Users/macmini/esp/esp-idf/tools/idf.py", line 1096, in execute_tasks
task.run(ctx, global_args, task.action_args)
File "/Users/macmini/esp/esp-idf/tools/idf.py", line 687, in run
self.callback(self.name, context, global_args, **action_args)
File "/Users/macmini/esp/esp-idf/tools/idf.py", line 328, in build_target
_run_tool(generator_cmd[0], generator_cmd + [target_name], args.build_dir)
File "/Users/macmini/esp/esp-idf/tools/idf.py", line 104, in _run_tool
subprocess.check_call(args, env=os.environ, cwd=cwd)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 535, in check_call
retcode = call(*popenargs, **kwargs)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 522, in call
return Popen(*popenargs, **kwargs).wait()
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 710, in init
errread, errwrite)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 1335, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

When I am trying to build the code for blinking the onboard LED, the following message is displayed:

"Building in: C:\Users\eclipse-workspace\blink\build
cmake -G Ninja -DCMAKE_TOOLCHAIN_FILE=C:\Users\Desktop\IDF\esp-idf-master\tools\cmake\toolchain-esp32.cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DIDF_TARGET=esp32 C:\Users\eclipse-workspace\blink
fatal: not a git repository (or any of the parent directories): .git
CMake Warning at C:/Users/Desktop/IDF/esp-idf-master/tools/cmake/kconfig.cmake:39 (message):
Failed to detect version of mconf-idf. Return code was 1.
Call Stack (most recent call first):
C:/Users/Desktop/IDF/esp-idf-master/tools/cmake/build.cmake:161 (__kconfig_init)
C:/Users/Desktop/IDF/esp-idf-master/tools/cmake/idf.cmake:48 (__build_init)
C:/Users/Desktop/IDF/esp-idf-master/tools/cmake/project.cmake:7 (include)
CMakeLists.txt:5 (include)

-- 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...
CMake Error at C:/Users/Desktop/IDF/esp-idf-master/tools/cmake/build.cmake:271 (message):
Some Python dependencies must be installed. Check above message for
details.
Call Stack (most recent call first):
C:/Users/Desktop/IDF/esp-idf-master/tools/cmake/build.cmake:397 (__build_check_python)
C:/Users/Desktop/IDF/esp-idf-master/tools/cmake/project.cmake:341 (idf_build_process)
CMakeLists.txt:6 (project)

-- Configuring incomplete, errors occurred!
See also "C:/Users/eclipse-workspace/blink/build/CMakeFiles/CMakeOutput.log".
See also "C:/Users/eclipse-workspace/blink/build/CMakeFiles/CMakeError.log".
cmake --build . -- -v
ninja: error: loading 'build.ninja': The system cannot find the file specified.

Build complete (0 errors, 0 warnings): C:\Users\eclipse-workspace\blink\build"

Kindly help me out!

Hi,
I did a fresh installation, ESP_IDF, eclipse and so on, the installation is now running fine however no #includes has been resolved and a build failed due missing bootloader.map file.

Hi there!

I am running Ubuntu 19.04 with Eclipse 2019-09.
I installed the latest ESP-IDF (by git clone, as described in the Get Started) and the latest Eclipse Plugin from the URL.
I installed the Tools with the "Install Tools"-command in Eclipse.

When trying to build a application, it said in the console:

Errors occurred during the build.
Errors running builder 'CDT Core Builder' on project 'hello_world'.
Building hello_world
Cannot run program "/home/alexanderp/esp/esp-idf/tools/cmake" (in directory "/home/alexanderp/eclipse-workspace/hello_world/build"): error=13, Permission denied
Building hello_world
Cannot run program "/home/alexanderp/esp/esp-idf/tools/cmake" (in directory "/home/alexanderp/eclipse-workspace/hello_world/build"): error=13, Permission denied

After examining my PATH variable, i found out, that the entry for the "cmake" - Tool was not automatically made during the installation of the tool.
PATH before:

/home/alexanderp/.espressif/tools/xtensa-esp32-elf/esp-2019r2-8.2.0/xtensa-esp32-elf/bin:
/home/alexanderp/.espressif/tools/xtensa-esp32s2-elf/esp-2019r2-8.2.0/xtensa-esp32s2-elf/bin:
/home/alexanderp/.espressif/tools/esp32ulp-elf/2.28.51.20170517/esp32ulp-elf-binutils/bin:
/home/alexanderp/.espressif/tools/openocd-esp32/v0.10.0-esp32-20190708/openocd-esp32/bin:/home/alexanderp/.espressif/tools/ninja/1.9.0/:
/home/alexanderp/.espressif/python_env/idf4.1_py2.7_env/bin:
/home/alexanderp/esp/esp-idf/tools:
/home/alexanderp/.local/bin:
/usr/local/sbin:
/usr/local/bin:
/usr/sbin:
/usr/bin:
/sbin:
/bin:
/usr/games:
/usr/local/games:
/snap/bin:

So after making the entry manually,

--> /home/alexanderp/.espressif/tools/cmake/3.13.4/bin: (manually added to PATH)

i was able to build and flash a application.

The problem is at step "Installing ESP-IDF Tools" the option "Espressif IDF Tools Manager" isn't there on the UI.

My system environment is:

• OSX Mojave
• Eclipse
  - Version: 2019-09 R (4.13.0)
  - Build id: 20190917-1200

I'm getting an error during the load process of the plugin. I did a manual download which generated other errors.

using open jdk 13 on mac 10.14.6
fresh checkout of esp idf v4.0-beta1
fresh install of eclipse 2019-09
fresh plugin install
installed tools using tools manager

I created a new project from hello_world example. I'm getting a bunch of "unresolved inclusion" and red highlights all over the editor. Of note, "#include <stdio.h>" is found, and when I open this file it's pulling it from this path: /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h

Building fails, and is missing PATH for ninja. The other tools are there.

Fixing PATH lets me build, but editor is still buggered.

I've tried going through the manual steps mentioned, but nothing seems to fix Eclipse's editor. I'm pretty sure its not using xtensa gcc when its generating these editor errors, and I would expect it to jump to the stdio.h from xtensa's gcc, not the system SDK.

Any help would be appreciated!

Describe the bug
Type 'esp_chip_info_t' could not be resolved
osx
eclipse 2019-12 cdt

To Reproduce
Steps to reproduce the behavior:

1. create a new idf project using hello_world template project;
2. add some include directories;
3. build success,but Type 'esp_chip_info_t' could not be resolved in hello_world_main.c file

Screenshots

Environment Information:
eclipse.info.txt

ESP-IDF Tools Information:
Executing /usr/bin/python /Users/fick/esp/esp-idf/tools/idf_tools.py list

• xtensa-esp32-elf: Toolchain for Xtensa (ESP32) based on GCC
  • esp-2019r2-8.2.0 (recommended, installed)
• xtensa-esp32s2-elf: Toolchain for Xtensa (ESP32-S2) based on GCC
  • esp-2019r2-8.2.0 (recommended, installed)
• esp32ulp-elf: Toolchain for ESP32 ULP coprocessor
  • 2.28.51-esp-20191205 (recommended, installed)
• esp32s2ulp-elf: Toolchain for ESP32-S2 ULP coprocessor
  • 2.28.51-esp-20191205 (recommended, installed)
• cmake: CMake build system (optional)
  • 3.13.4 (recommended, installed)
• openocd-esp32: OpenOCD for ESP32
  • v0.10.0-esp32-20191114 (recommended, installed)
• ninja: Ninja build system (optional)
  • 1.9.0 (recommended, installed)

Hi.

After I successfully build the hello world project, eclipse is still showing unresolved references and unknown variables. The error view also still mentions errors:

Same build:

after building and flashing successfully the blink template I see still unresolved inclusions in my source file.
eclipse project has been created via https://github.com/espressif/idf-eclipse-plugin#create-a-new-project-using-esp-idf-templates

I use "latest" espressif plugin (see attached file)

I expect inclusions to be resolved after building for target

Environment Information:
eclipse info.log

ESP-IDF Tools Information:
Executing C:\Users\hpd\AppData\Local\Programs\Python\Python37\python.exe C:\Users\hpd\Documents\HPDPool\Privat\HpdDev2020\ESP32\ESPV4\tools\idf_tools.py list

• xtensa-esp32-elf: Toolchain for Xtensa (ESP32) based on GCC
  • esp-2019r2-8.2.0 (recommended, installed)
• esp32ulp-elf: Toolchain for ESP32 ULP coprocessor
  • 2.28.51.20170517 (recommended, installed)
• cmake: CMake build system
  • 3.13.4 (recommended, installed)
• openocd-esp32: OpenOCD for ESP32
  • v0.10.0-esp32-20190313 (recommended, installed)
• mconf: menuconfig tool
  • v4.6.0.0-idf-20190628 (recommended, installed)
• ninja: Ninja build system
  • 1.9.0 (recommended, installed)
• idf-exe: IDF wrapper tool for Windows
  • 1.0.1 (recommended, installed)
• ccache: Ccache (compiler cache)
  • 3.7 (recommended, installed)

esp-idf-v.3.3 support cmake and had "Long Term Support".
When idf-eclipse-plugin will support esp-idf-v3.3 ?

Without this we cannot use esp-idf with Arduino.h component in Eclipse. Because the only last branch of arduino-esp32 we have is (idf-release/v3.3).

When double clicking on the sdkconfig, it will prompt a dialog stating "Starting JSON Configuration Server" and the it will failed with a message on a new tab:

"Error retrieving output from the json configserver, please check the error log"

The Error Log windows does not show any error details.

building esp-idf project with pure make you can specify include directories with the item

how can it be defined in the idf-eclipse plugin as there i cant find such entry

When using Eclipse to install the idf tools I get the following python errors:

Executing D:\Python36\python.exe D:\EPS-IDF\tools\idf_tools.py install-python-env
fatal: not a git repository (or any of the parent directories): .git
Traceback (most recent call last):
File "D:\EPS-IDF\tools\idf_tools.py", line 1317, in
main(sys.argv[1:])
File "D:\EPS-IDF\tools\idf_tools.py", line 1313, in main
action_func(args)
File "D:\EPS-IDF\tools\idf_tools.py", line 1112, in action_install_python_env
idf_python_env_path, _, virtualenv_python = get_python_env_path()
File "D:\EPS-IDF\tools\idf_tools.py", line 813, in get_python_env_path
idf_version_str = subprocess.check_output(['git', '-C', global_idf_path, 'describe', '--tags'], cwd=global_idf_path, env=os.environ).decode()
File "D:\Python36\lib\subprocess.py", line 336, in check_output
**kwargs).stdout
File "D:\Python36\lib\subprocess.py", line 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', '-C', 'D:\EPS-IDF', 'describe', '--tags']' returned non-zero exit status 128.

Executing D:\Python36\python.exe D:\EPS-IDF\tools\idf_tools.py export --format=key-value
fatal: not a git repository (or any of the parent directories): .git
Not using an unsupported version of tool cmake found in PATH: 3.15.0. To use it, run 'D:\Python36\python.exe D:\EPS-IDF\tools\idf_tools.py export --prefer-system'
Traceback (most recent call last):
File "D:\EPS-IDF\tools\idf_tools.py", line 1317, in
main(sys.argv[1:])
File "D:\EPS-IDF\tools\idf_tools.py", line 1313, in main
action_func(args)
File "D:\EPS-IDF\tools\idf_tools.py", line 953, in action_export
idf_python_env_path, idf_python_export_path, virtualenv_python = get_python_env_path()
File "D:\EPS-IDF\tools\idf_tools.py", line 813, in get_python_env_path
idf_version_str = subprocess.check_output(['git', '-C', global_idf_path, 'describe', '--tags'], cwd=global_idf_path, env=os.environ).decode()
File "D:\Python36\lib\subprocess.py", line 336, in check_output
**kwargs).stdout
File "D:\Python36\lib\subprocess.py", line 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', '-C', 'D:\EPS-IDF', 'describe', '--tags']' returned non-zero exit status 128.

I used python 3.6 64-bit and Eclipse 2019-09 on Windows 10

Hi All,

Initially thank you for you incredible work.
I was trying to installl it on Windows 10, in fact I'm able to compile and flash the ESP32. However the Install Tools and List Installed Tools are not working.

I'm facing the follow error:
`!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)`

I double checked my python installation and everything is fine (Python 3.7.4) in the register.

I'm not a Java expert, but debuging the class PyWinRegistryReader, I noted that the failure is before start to access the Windows Register, I face the follow error:
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:48) at PyWinRegistryReader.main(PyWinRegistryReader.java:96) null

So, I'm still trying to understand whats is going on.

Hello!

I cant install tools. I get this error:

Does anyone have an idea for a solution?
Use :
-java 8
-eclipse 2019-09
-esp-idf v4 and v4.1

NOTE: Github is requires I put down the "Eclipse Environment" in an attachment.

Describe the bug
Execute BUILD under Eclipse fails with Some Python dependencies must be installed...

This is caused by something unique in the ESP build system or plugin modifying the PATH variable when executing CMAKE.

To Reproduce
Steps to reproduce the behavior:

1. Run the "env.sh" script to set tools variables. (I do not have these in my .profile), I run the script when I need these variables set.

2. On MACOS, to launch Eclipse from the command line, type:

/Applications/Eclipse.app/Contents/MacOS/eclipse

3. Import any generic simple project and attempt to build.

The build fails, with ```Some Python dependencies must be installed``

4. Exit Eclipse, and build from the command line

for example, type:

cmake -G Ninja -DCMAKE_EXPORT_COMPILE_COMMANDS=ON /Users/mynamehere/ESP32/eclipse-project1

RESULT: it works

5. Upon further inspection (I modified the CMAKE file to print the Shell Environment variables) and determined that either (A) eclipse, or (B) the EXPRESSIF plugin, or (C) the CDT build system forcibly places/inserts: /usr/bin at the front of the PATH variable before executing the build.

This causes the following problem:

When I run the env.sh script the EXPRESSIF version of PYTHON is first in my PATH, thus things work correctly from the command line.

When run from inside Eclipse - Because /usr/bin is inserted by something (A, B, or C above) the system provided python is found instead, which does not have the required features installed.

IN CONTRAST

If I launch other tools, such as the editor Emacs, ie: /Applications/Emacs/Content/MacOS/emacs this same way, the shell variables are NOT modified.

It is only eclipse that inserts /usr/bin in my PATH.

Environment Information:

(See attached

eclipse-env.txt

ESP-IDF Tools Information:
Help > Espressif Tools Manager > List Installed Tools

See attached: eclipse-env.txt

NOTE See right here - where it executes /usr/bin/python not the IDF python!

Executing /usr/bin/python /Users/duane/ESP32/esp-idf/tools/idf_tools.py list

• xtensa-esp32-elf: Toolchain for Xtensa (ESP32) based on GCC
  • esp-2019r2-8.2.0 (recommended, installed)
• xtensa-esp32s2-elf: Toolchain for Xtensa (ESP32-S2) based on GCC
  • esp-2019r2-8.2.0 (recommended, installed)
• esp32ulp-elf: Toolchain for ESP32 ULP coprocessor
  • 2.28.51.20170517 (recommended, installed)
• cmake: CMake build system (optional)
  • 3.13.4 (recommended, installed)
• openocd-esp32: OpenOCD for ESP32
  • v0.10.0-esp32-20190708 (recommended, installed)
• ninja: Ninja build system (optional)
  • 1.9.0 (recommended, installed)

When attempting the "Installing IDF Plugins using update site url" method, the url provided ( https://dl.espressif.com/dl/idf-eclipse-plugin/updates/latest/) results in a 403 error.

When attempting the "Installing IDF Plugins from Local" method, there are no files in the Releases directory.

Hello,
While installing the Help > Espressif IDF Tools Manager > Install Tools in the Eclipse
(Eclipse IDE for C/C++ Developers Version: 2019-12 (4.14.0), the installation is keep running for more than 24 hours.

Steps to reproduce:

• I followed the instruction in the https://github.com/espressif/idf-eclipse-plugin
• Downloaded the local folder
• Provided the ESP-IDF Directory path to get started with the installation and.... after this the message in the right bottom of the Eclipse keep running xxx of 256 MB and i waited for 24 hours !

• Got the local from :
  https://dl.espressif.com/dl/idf-eclipse-plugin/updates/com.espressif.idf.update-v999-24-g120495da.zip

Any help?

Thanks in advance
Shanmuganathan

From the install page
https://github.com/espressif/idf-eclipse-plugin

Under Prerequisites, it says:
ESP-IDF 4.0 and above : Follow the download instructions from here

That page tells you to download the " ESP-IDF Tools Installer ". Yet when you run that there is no 4.0 option.

When trying to do the simple build of "hello world" example. I got this failure

Building in: /home/lieven/workspace/esp-idf-test/build
cmake -G Ninja -DCMAKE_TOOLCHAIN_FILE=/home/lieven/esp/esp-idf/tools/cmake/toolchain-esp32.cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DIDF_TARGET=esp32 /home/lieven/workspace/esp-idf-test
-- Checking Python dependencies...
Python requirements from /home/lieven/esp/esp-idf/requirements.txt are satisfied.
-- Building for target esp32
CMake Error: CMake was unable to find a build program corresponding to "Ninja". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool.
-- Configuring incomplete, errors occurred!
See also "/home/lieven/workspace/esp-idf-test/build/CMakeFiles/CMakeOutput.log".
cmake --build . -- -v
No such file or directory
CMake Error: Generator: execution of make failed. Make command was: "" "-v"
Build complete (0 errors, 0 warnings): /home/lieven/workspace/esp-idf-test/build

Similar to: 'ESP-IDF Directory selection dialog doesn't appear #2'

"I followed step by step the instruction. Installed the plugin using URL method. Then I go to: Help > Espressif IDF Tools Manager > Install Tools and after pushing install nothing happens. Directory selection dialog doesn't appear."

After installing with v1.0.0-beta.2

Eclipse:
Version: 2019-09 R (4.13.0)
Build id: 20190917-1200
Python: 3.80
Java SE Development Kit 13

Any thoughts about the cause of the trouble?
Thanks in advance, Ralph

I use Eclipse 2019-09 and configured everything as described.
I can debug my esp32, i can step trough my code etc

But the actual line in the eclipse editor is not highlighted which is a little bit anoying as i can't really see where i am in my code

This is the openocd output after some breakpoint hits

** Programming Started **
auto erase enabled
Info : Target halted. PRO_CPU: PC=0x4009171A (active)    APP_CPU: PC=0x40000400
Info : Target halted. PRO_CPU: PC=0x4009171A (active)    APP_CPU: PC=0x40000400
wrote 155648 bytes from file D:/esp/projects/testdebug/build/blink.bin in 2.159124s (70.399 KiB/s)
** Programming Finished **
** Verify Started **
Info : Target halted. PRO_CPU: PC=0x4009171A (active)    APP_CPU: PC=0x40000400
read 151936 bytes from file D:/esp/projects/testdebug/build/blink.bin and flash bank 0 at offset 0x00010000 in 0.808046s (183.622 KiB/s)
contents match
** Verified OK **
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32: Debug controller 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : Target halted. PRO_CPU: PC=0x5000004B (active)    APP_CPU: PC=0x00000000
Info : esp32: Core 0 was reset (pwrstat=0x1F, after clear 0x0F).
Info : esp32: Debug controller 1 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 1 was reset (pwrstat=0x5F, after clear 0x0F).
Info : Target halted. PRO_CPU: PC=0x40000400 (active)    APP_CPU: PC=0x40000400
Info : Detected debug stubs @ 3ffb2a90 on core0 of target 'esp32'
Info : Target halted. PRO_CPU: PC=0x400D3B90 (active)    APP_CPU: PC=0x400E2D12
Info : Target halted. PRO_CPU: PC=0x400D3BE6 (active)    APP_CPU: PC=0x400E2D12
Info : Target halted. PRO_CPU: PC=0x400D3BE6 (active)    APP_CPU: PC=0x400E2D12

List of installed tools and plugin

Espressif IDF Plugins for Eclipse 1.0.0.201912090756 com.espressif.idf.feature.feature.group ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD

Executing C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\python.exe D:\esp\idf\tools\idf_tools.py list
* xtensa-esp32-elf: Toolchain for Xtensa (ESP32) based on GCC
  - esp-2019r2-8.2.0 (recommended, installed)
* esp32ulp-elf: Toolchain for ESP32 ULP coprocessor
  - 2.28.51.20170517 (recommended, installed)
* cmake: CMake build system
  - 3.13.4 (recommended, installed)
* openocd-esp32: OpenOCD for ESP32
  - v0.10.0-esp32-20190313 (recommended, installed)
* mconf: menuconfig tool
  - v4.6.0.0-idf-20190628 (recommended, installed)
* ninja: Ninja build system
  - 1.9.0 (recommended, installed)
* idf-exe: IDF wrapper tool for Windows
  - 1.0.1 (recommended, installed)
* ccache: Ccache (compiler cache)
  - 3.7 (recommended, installed)

Do you have any idea what might be wrong? I can provide further details if needed

Hi,

On a windows 10 system with the latest python/git/pip I can't build the tools in eclipse 19-09. I can build them with the install and export batch files with the 'default' tools and old versions. I noticed in the console that the path to python seems to be hardcoded. Python is installed for all users in Roaming not Local. The environmental PATH is correctly set. The path to the python file is correct. I have another windows 10 system working so for me it's a minor issue.
Thanks for the great work.

Regards,

Rob.

Java: 1.8
Eclipse: 2019-09
OS: Windows 10
python: 3.8
esp-idf: 4.0-beta1

Hello.

Trying to work with new eclipse plugin, I can't get it. Following readme.md guide, I have everything installed and tools installation console output doesn't show any error. However, when I try to compile any example, console shows that 'requiments.txt' dependencies can't be found.

Trying with 'install.bat' or 'C:\Users\JM\.espressif\python_env\idf4.0_py3.8_env\Scripts\python.exe -m pip install -r D:\esp-idf\requirements.txt' on windows cmd, cryptography dependency shows error.

First error is related with Microsoft C++ Build Tools 14.0. I resolved it adding C++ tools into my Visual Studio 2019 installation. But now, I have another error I can't resolve:

C:\Windows\system32>C:\\Users\\JM\\.espressif\\python_env\\idf4.0_py3.8_env\\Scripts\\python.exe -m pip install -r D:\\esp-idf\\requirements.txt
Requirement already satisfied: setuptools in c:\users\jm\.espressif\python_env\idf4.0_py3.8_env\lib\site-packages (from -r D:\\esp-idf\\requirements.txt (line 4)) (41.4.0)
Requirement already satisfied: click>=5.0 in c:\users\jm\.espressif\python_env\idf4.0_py3.8_env\lib\site-packages (from -r D:\\esp-idf\\requirements.txt (line 8)) (7.0)
Requirement already satisfied: pyserial>=3.0 in c:\users\jm\.espressif\python_env\idf4.0_py3.8_env\lib\site-packages (from -r D:\\esp-idf\\requirements.txt (line 9)) (3.4)
Requirement already satisfied: future>=0.15.2 in c:\users\jm\.espressif\python_env\idf4.0_py3.8_env\lib\site-packages (from -r D:\\esp-idf\\requirements.txt (line 10)) (0.18.0)
Collecting cryptography>=2.1.4
  Using cached https://files.pythonhosted.org/packages/c2/95/f43d02315f4ec074219c6e3124a87eba1d2d12196c2767fadfdc07a83884/cryptography-2.7.tar.gz
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
    Preparing wheel metadata ... done
Requirement already satisfied: pyparsing<2.4.0,>=2.0.3 in c:\users\jm\.espressif\python_env\idf4.0_py3.8_env\lib\site-packages (from -r D:\\esp-idf\\requirements.txt (line 12)) (2.3.1)
Requirement already satisfied: pyelftools>=0.22 in c:\users\jm\.espressif\python_env\idf4.0_py3.8_env\lib\site-packages (from -r D:\\esp-idf\\requirements.txt (line 13)) (0.25)
Collecting six>=1.4.1
  Using cached https://files.pythonhosted.org/packages/73/fb/00a976f728d0d1fecfe898238ce23f502a721c0ac0ecfedb80e0d88c64e9/six-1.12.0-py2.py3-none-any.whl
Collecting asn1crypto>=0.21.0
  Using cached https://files.pythonhosted.org/packages/6b/8c/ff300484eca90b397d919408619fae479965bdd8a1df3d6d08d58e491da5/asn1crypto-1.2.0-py2.py3-none-any.whl
Collecting cffi!=1.11.3,>=1.8
  Using cached https://files.pythonhosted.org/packages/c9/a5/7f5b85daf1992172d7b84e2a17dd66b5a9577018fc6063d7bacfc0b97e14/cffi-1.13.0-cp38-cp38-win_amd64.whl
Processing c:\users\jm\appdata\local\pip\cache\wheels\f2\9a\90\de94f8556265ddc9d9c8b271b0f63e57b26fb1d67a45564511\pycparser-2.19-py2.py3-none-any.whl
Building wheels for collected packages: cryptography
  Building wheel for cryptography (PEP 517) ... error
  ERROR: Command errored out with exit status 1:
   command: 'C:\Users\JM\.espressif\python_env\idf4.0_py3.8_env\Scripts\python.exe' 'C:\Users\JM\.espressif\python_env\idf4.0_py3.8_env\lib\site-packages\pip\_vendor\pep517\_in_process.py' build_wheel 'C:\Users\JM\AppData\Local\Temp\tmpojr1z10m'
       cwd: C:\Users\JM\AppData\Local\Temp\pip-install-dnuej4f1\cryptography
  Complete output (136 lines):
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build\lib.win-amd64-3.8
  creating build\lib.win-amd64-3.8\cryptography
  copying src\cryptography\exceptions.py -> build\lib.win-amd64-3.8\cryptography
  copying src\cryptography\fernet.py -> build\lib.win-amd64-3.8\cryptography
  copying src\cryptography\utils.py -> build\lib.win-amd64-3.8\cryptography
  copying src\cryptography\__about__.py -> build\lib.win-amd64-3.8\cryptography
  copying src\cryptography\__init__.py -> build\lib.win-amd64-3.8\cryptography
  creating build\lib.win-amd64-3.8\cryptography\hazmat
  copying src\cryptography\hazmat\_oid.py -> build\lib.win-amd64-3.8\cryptography\hazmat
  copying src\cryptography\hazmat\__init__.py -> build\lib.win-amd64-3.8\cryptography\hazmat
  creating build\lib.win-amd64-3.8\cryptography\x509
  copying src\cryptography\x509\base.py -> build\lib.win-amd64-3.8\cryptography\x509
  copying src\cryptography\x509\certificate_transparency.py -> build\lib.win-amd64-3.8\cryptography\x509
  copying src\cryptography\x509\extensions.py -> build\lib.win-amd64-3.8\cryptography\x509
  copying src\cryptography\x509\general_name.py -> build\lib.win-amd64-3.8\cryptography\x509
  copying src\cryptography\x509\name.py -> build\lib.win-amd64-3.8\cryptography\x509
  copying src\cryptography\x509\ocsp.py -> build\lib.win-amd64-3.8\cryptography\x509
  copying src\cryptography\x509\oid.py -> build\lib.win-amd64-3.8\cryptography\x509
  copying src\cryptography\x509\__init__.py -> build\lib.win-amd64-3.8\cryptography\x509
  creating build\lib.win-amd64-3.8\cryptography\hazmat\backends
  copying src\cryptography\hazmat\backends\interfaces.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends
  copying src\cryptography\hazmat\backends\__init__.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends
  creating build\lib.win-amd64-3.8\cryptography\hazmat\bindings
  copying src\cryptography\hazmat\bindings\__init__.py -> build\lib.win-amd64-3.8\cryptography\hazmat\bindings
  creating build\lib.win-amd64-3.8\cryptography\hazmat\primitives
  copying src\cryptography\hazmat\primitives\cmac.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives
  copying src\cryptography\hazmat\primitives\constant_time.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives
  copying src\cryptography\hazmat\primitives\hashes.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives
  copying src\cryptography\hazmat\primitives\hmac.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives
  copying src\cryptography\hazmat\primitives\keywrap.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives
  copying src\cryptography\hazmat\primitives\padding.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives
  copying src\cryptography\hazmat\primitives\poly1305.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives
  copying src\cryptography\hazmat\primitives\__init__.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives
  creating build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\aead.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\backend.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\ciphers.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\cmac.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\decode_asn1.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\dh.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\dsa.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\ec.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\ed25519.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\ed448.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\encode_asn1.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\hashes.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\hmac.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\ocsp.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\poly1305.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\rsa.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\utils.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\x25519.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\x448.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\x509.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  copying src\cryptography\hazmat\backends\openssl\__init__.py -> build\lib.win-amd64-3.8\cryptography\hazmat\backends\openssl
  creating build\lib.win-amd64-3.8\cryptography\hazmat\bindings\openssl
  copying src\cryptography\hazmat\bindings\openssl\binding.py -> build\lib.win-amd64-3.8\cryptography\hazmat\bindings\openssl
  copying src\cryptography\hazmat\bindings\openssl\_conditional.py -> build\lib.win-amd64-3.8\cryptography\hazmat\bindings\openssl
  copying src\cryptography\hazmat\bindings\openssl\__init__.py -> build\lib.win-amd64-3.8\cryptography\hazmat\bindings\openssl
  creating build\lib.win-amd64-3.8\cryptography\hazmat\primitives\asymmetric
  copying src\cryptography\hazmat\primitives\asymmetric\dh.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\asymmetric
  copying src\cryptography\hazmat\primitives\asymmetric\dsa.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\asymmetric
  copying src\cryptography\hazmat\primitives\asymmetric\ec.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\asymmetric
  copying src\cryptography\hazmat\primitives\asymmetric\ed25519.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\asymmetric
  copying src\cryptography\hazmat\primitives\asymmetric\ed448.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\asymmetric
  copying src\cryptography\hazmat\primitives\asymmetric\padding.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\asymmetric
  copying src\cryptography\hazmat\primitives\asymmetric\rsa.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\asymmetric
  copying src\cryptography\hazmat\primitives\asymmetric\utils.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\asymmetric
  copying src\cryptography\hazmat\primitives\asymmetric\x25519.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\asymmetric
  copying src\cryptography\hazmat\primitives\asymmetric\x448.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\asymmetric
  copying src\cryptography\hazmat\primitives\asymmetric\__init__.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\asymmetric
  creating build\lib.win-amd64-3.8\cryptography\hazmat\primitives\ciphers
  copying src\cryptography\hazmat\primitives\ciphers\aead.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\ciphers
  copying src\cryptography\hazmat\primitives\ciphers\algorithms.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\ciphers
  copying src\cryptography\hazmat\primitives\ciphers\base.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\ciphers
  copying src\cryptography\hazmat\primitives\ciphers\modes.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\ciphers
  copying src\cryptography\hazmat\primitives\ciphers\__init__.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\ciphers
  creating build\lib.win-amd64-3.8\cryptography\hazmat\primitives\kdf
  copying src\cryptography\hazmat\primitives\kdf\concatkdf.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\kdf
  copying src\cryptography\hazmat\primitives\kdf\hkdf.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\kdf
  copying src\cryptography\hazmat\primitives\kdf\kbkdf.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\kdf
  copying src\cryptography\hazmat\primitives\kdf\pbkdf2.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\kdf
  copying src\cryptography\hazmat\primitives\kdf\scrypt.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\kdf
  copying src\cryptography\hazmat\primitives\kdf\x963kdf.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\kdf
  copying src\cryptography\hazmat\primitives\kdf\__init__.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\kdf
  creating build\lib.win-amd64-3.8\cryptography\hazmat\primitives\serialization
  copying src\cryptography\hazmat\primitives\serialization\base.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\serialization
  copying src\cryptography\hazmat\primitives\serialization\pkcs12.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\serialization
  copying src\cryptography\hazmat\primitives\serialization\ssh.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\serialization
  copying src\cryptography\hazmat\primitives\serialization\__init__.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\serialization
  creating build\lib.win-amd64-3.8\cryptography\hazmat\primitives\twofactor
  copying src\cryptography\hazmat\primitives\twofactor\hotp.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\twofactor
  copying src\cryptography\hazmat\primitives\twofactor\totp.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\twofactor
  copying src\cryptography\hazmat\primitives\twofactor\utils.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\twofactor
  copying src\cryptography\hazmat\primitives\twofactor\__init__.py -> build\lib.win-amd64-3.8\cryptography\hazmat\primitives\twofactor
  running egg_info
  writing src\cryptography.egg-info\PKG-INFO
  writing dependency_links to src\cryptography.egg-info\dependency_links.txt
  writing requirements to src\cryptography.egg-info\requires.txt
  writing top-level names to src\cryptography.egg-info\top_level.txt
  reading manifest file 'src\cryptography.egg-info\SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  no previously-included directories found matching 'docs\_build'
  warning: no previously-included files found matching 'vectors'
  warning: no previously-included files matching '*' found under directory 'vectors'
  warning: no previously-included files found matching 'azure-pipelines.yml'
  warning: no previously-included files found matching '.azure-pipelines'
  warning: no previously-included files found matching '.travis.yml'
  warning: no previously-included files found matching '.travis'
  warning: no previously-included files matching '*' found under directory '.azure-pipelines'
  warning: no previously-included files matching '*' found under directory '.travis'
  warning: no previously-included files found matching 'release.py'
  warning: no previously-included files found matching '.coveragerc'
  warning: no previously-included files found matching 'codecov.yml'
  warning: no previously-included files found matching 'dev-requirements.txt'
  warning: no previously-included files found matching 'rtd-requirements.txt'
  warning: no previously-included files found matching 'tox.ini'
  writing manifest file 'src\cryptography.egg-info\SOURCES.txt'
  running build_ext
  generating cffi module 'build\\temp.win-amd64-3.8\\Release\\_padding.c'
  creating build\temp.win-amd64-3.8
  creating build\temp.win-amd64-3.8\Release
  generating cffi module 'build\\temp.win-amd64-3.8\\Release\\_constant_time.c'
  generating cffi module 'build\\temp.win-amd64-3.8\\Release\\_openssl.c'
  building '_openssl' extension
  creating build\temp.win-amd64-3.8\Release\build
  creating build\temp.win-amd64-3.8\Release\build\temp.win-amd64-3.8
  creating build\temp.win-amd64-3.8\Release\build\temp.win-amd64-3.8\Release
  C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.23.28105\bin\HostX86\x64\cl.exe /c /nologo /Ox /W3 /GL /DNDEBUG /MD -IC:\Users\JM\AppData\Local\Programs\Python\Python38\include -IC:\Users\JM\AppData\Local\Programs\Python\Python38\include "-IC:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.23.28105\include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\cppwinrt" /Tcbuild\temp.win-amd64-3.8\Release\_openssl.c /Fobuild\temp.win-amd64-3.8\Release\build\temp.win-amd64-3.8\Release\_openssl.obj
  _openssl.c
  build\temp.win-amd64-3.8\Release\_openssl.c(498): fatal error C1083: No se puede abrir el archivo incluir: 'openssl/opensslv.h': No such file or directory
  error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\BuildTools\\VC\\Tools\\MSVC\\14.23.28105\\bin\\HostX86\\x64\\cl.exe' failed with exit status 2
  ----------------------------------------
  ERROR: Failed building wheel for cryptography
  Running setup.py clean for cryptography
Failed to build cryptography
ERROR: Could not build wheels for cryptography which use PEP 517 and cannot be installed directly

Can you point me to obtain a solution??

Thanks in advance.

The following is displayed to me if I choose Help -> Espressif IDF Tools Manager -> Install Tools

I used the newest java version, I also tryed it with java8u221 - same result.

I used url to install the idf-eclipse-plugin from
https://dl.espressif.com/dl/idf-eclipse-plugin/updates/latest/
but i also tryed local installation with
idf-eclipse-plugin-v1.0.0-beta.2
also the same result.

Could you help me please?

Exception Stack Trace:
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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
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:488)
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:4175)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3988)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3587)
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:660)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:559)
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:401)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
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)

Description

I'm trying to setup my environment in Eclipse to run the Hello World project by following the steps from:

https://github.com/espressif/idf-eclipse-plugin/blob/master/README.md

But when I get to:

https://github.com/espressif/idf-eclipse-plugin/blob/master/README.md#installing-esp-idf-tools

The steps are not the same as the ones show in the latest IDF-Eclipse-Plugin. In the tutorial you can see that is only required to add the path to the IDF and now you need also to add the path for "Git Executable Location".

Screenshots

NOW

CURRRENT TUTORIAL

Hey!

I downloaded Mosquitto and successfully transmitted and received messages sent using command prompt. However, while trying to build a code on Eclipse throws me errors; primarily that the mosquitto.h is missing. Kindly help.

ERROR SNIPPET:

CODE: (reference: Kolban's book on ESP32)

#include "freertos/FreeRTOS.h"
#include "esp_wifi.h"
#include "esp_system.h"
#include "esp_event.h"
#include "esp_event_loop.h"
#include "nvs_flash.h"
#include "driver/gpio.h"
#include <stdio.h>
#include <string.h>
#include "mosquitto.h"

int app_main(int argc, char *argv[])
{
char *host="pc9100";
int port = 1883;
char *message = "hello world!";
char *topic = "greeting";

 mosquitto_lib_init();
 struct mosquitto *mosq = mosquitto_new(
		 NULL,  // Generate an id
		 true,  // Create a clean session
		 NULL);

 int rc = mosquitto_connect(
		 	 mosq,   // Client handle
			 host,   // Host of the broker
			 port,   // Port of the broker
			 false);

 if (rc != MOSQ_ERR_SUCCESS)
 {
	 printf("Error with connect: %d\n", rc);
	 return(rc);
 }

 mosquitto_publish(
		 mosq,
		 NULL,
		 topic,
		 strlen(message)+1;
 	 	 (const void*)message,
 	 	0,
		false);

 mosquitto_destroy(mosq);
 mosquitto_clean_up;

}

Using the ulp template project I get this:

ulp.txt

It looks like the ULP toolchain is installed but I'm not sure.
Question: Is it possible to use Eclipse for a ulp project?

If I press (F3) while having cursor pointed to a function call like

esp_mqtt_client_publish(mqtt_client, CONFIG_EXAMPLE_PUBLISH_TOPIC, buf , strlen(buf), 1, 0);

I expect the type definition to be shown and after further (F3) , the implementation of this function to be shown.

But after showing Type definition as expected, the second (F3) will not show me the function implementation.

Meanwhile i learned, that {STRG}{TAB} at least will bring up the source file where a function is implemented. But this works only, if the function's source file has the same name as the header file and is as well located in the same directory.

I am using Eclipse 19-09 with ESP-IDF-ECLIPSE-PLUGIN (Beta 4).

Executing C:\Users\hpd\AppData\Local\Programs\Python\Python37\python.exe C:\Users\hpd\Documents\HPDPool\Privat\HpdDev2020\ESP32\ESPV4\tools\idf_tools.py list

• xtensa-esp32-elf: Toolchain for Xtensa (ESP32) based on GCC
  • esp-2019r2-8.2.0 (recommended, installed)
• esp32ulp-elf: Toolchain for ESP32 ULP coprocessor
  • 2.28.51.20170517 (recommended, installed)
• cmake: CMake build system
  • 3.13.4 (recommended, installed)
• openocd-esp32: OpenOCD for ESP32
  • v0.10.0-esp32-20190313 (recommended, installed)
• mconf: menuconfig tool
  • v4.6.0.0-idf-20190628 (recommended, installed)
• ninja: Ninja build system
  • 1.9.0 (recommended, installed)
• idf-exe: IDF wrapper tool for Windows
  • 1.0.1 (recommended, installed)
• ccache: Ccache (compiler cache)
  • 3.7 (recommended, installed)

Hi.

I tried to install the BETA3 package manually with the following error:

• Installation selection: