Create a new project Error in platfromio ide with vscode! When modify the folder path of .platformio from "%HOMEPATH%\.platfromio" to Specified path

hi, i want modify the folder path of .platformio from “HOMEPATH%.platformio” to Specified path, as i know i have follow these step, the operation sequence as below

1.) uninstall platformio extensions
2.) removed the forders of these path “%HOMEPATH%.vscode\extensions\platformio.platformio-ide-2.2.1” and “%HOMEPATH%.platformio”
3.) seting system environment variable “PLATFORMIO_CORE_DIR=D:\CodeDeveloper\Platformio”
4.) uninstall Visual Studio Code then restart computer when finished uninstall.
5.) removed “%HOMEPATH%.vscode” forder.
6.) install Visual Studio Code
7.) install extensions of platformio ide in vscode
8.) install embedded platform espressif32 in vscode of platformio extensions.
9.) finally create a new project.

but In this step, that can not be correctly create a new project and vscode show error message just like this -------->

PIO Core Call Error: "The current working directory E:\\Embed\\PlatformIO\\ESP32\\ttnnggf will be used for the project.
The next files/directories have been created in E:\\Embed\\PlatformIO\\ESP32\\ttnnggf
include - Put project header files here
lib - Put here project specific (private) libraries
nsrc - Put project source files here\r\nplatformio.ini - Project Configuration File
Error: Processing esp32doit-devkit-v1 (platform: espressif32; board: esp32doit-devkit-v1; framework: espidf)
Tool Manager: Installing platformio/toolchain-xtensa32 @ ~2.80400.0
Tool Manager: toolchain-xtensa32 @ 2.80400.210211 has been installed!
Tool Manager: Installing platformio/toolchain-esp32ulp @ ~1.22851.0
Tool Manager: toolchain-esp32ulp @ 1.22851.191205 has been installed!
Tool Manager: Installing platformio/framework-espidf @ ~3.40200.0
Tool Manager: framework-espidf @ 3.40200.210118 has been installed!\r\nTool Manager: Installing platformio/tool-cmake @ ~3.16.0
Tool Manager: tool-cmake @ 3.16.4 has been installed!\r\nTool Manager: Installing platformio/tool-ninja @ ^1.7.0
Tool Manager: tool-ninja @ 1.9.0 has been installed!\r\nTool Manager: Installing platformio/tool-mconf @ ~1.4060000.0
Tool Manager: tool-mconf @ 1.4060000.20190628 has been installed!\r\nTool Manager: Installing platformio/tool-idf @ ~1.0.1
Tool Manager: tool-idf @ 1.0.1 has been installed!\r\nTool Manager: Installing platformio/tool-scons @ ~4.40100.2
Tool Manager: tool-scons @ 4.40100.2 has been installed!\r\nVerbose mode can be enabled via `-v, --verbose` option
PLATFORM: Espressif 32 (3.0.0) > DOIT ESP32 DEVKIT V1\r\nHARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (esp-prog) External (esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
- framework-espidf 3.40200.210118 (4.2.0)
- tool-cmake 3.16.4
- tool-esptoolpy 1.30000.201119 (3.0.0)
- tool-idf 1.0.1
- tool-mconf 1.4060000.20190628 (406.0.0)
- tool-ninja 1.9.0
- toolchain-esp32ulp 1.22851.191205 (2.28.51)
- toolchain-xtensa32 2.80400.210211 (8.4.0)
  Installing ESP-IDF's Python dependencies
 Collecting cryptography>=2.1.4
 Using cached cryptography-3.4.6-cp36-abi3-win_amd64.whl (1.6 MB)
Collecting future>=0.15.2
Using cached future-0.18.2-py3-none-any.whl
Collecting pyparsing<2.4.0,>=2.0.3
 Using cached pyparsing-2.3.1-py2.py3-none-any.whl (61 kB)
Collecting cffi>=1.12
 Using cached cffi-1.14.5-cp37-cp37m-win_amd64.whl (178 kB)
Collecting pycparser
 Using cached pycparser-2.20-py2.py3-none-any.whl (112 kB)
Installing collected packages: pycparser, cffi, pyparsing, future, cryptography
Successfully installed cffi-1.14.5 cryptography-3.4.6 future-0.18.2 pycparser-2.20 pyparsing-2.3.1
Installing windows-curses package
Processing d:\\codedeveloper\\platformio\\packages\\framework-espidf\\tools\\kconfig_new\\esp-windows-curses
Collecting windows-curses
 Using cached windows_curses-2.2.0-cp37-cp37m-win_amd64.whl (70 kB)
Building wheels for collected packages: esp-windows-curses
 Building wheel for esp-windows-curses ( started
 Building wheel for esp-windows-curses ( finished with status 'done'
 Created wheel for esp-windows-curses: filename=esp_windows_curses-0.1-py3-none-any.whl size=1170 sha256=dbf70f333ea3ed2d87b585e045183a6599c999ef4c9be82f3e15af328876d565
Stored in directory: c:\\users\\administrator\\appdata\\local\\pip\\cache\\wheels\\45\\95\\62\\be4f6e51658f35c50e858ab580290dc19a4796716528d6dd4b
Successfully built esp-windows-curses
Installing collected packages: windows-curses, esp-windows-curses
Successfully installed esp-windows-curses-0.1 windows-curses-2.2.0
Reading CMake configuration...
*** Multiple ways to build the same target were specified for: E:\\Embed\\PlatformIO\\ESP32\\ttnnggf\\.pio\\build\\esp32doit-devkit-v1\\esp_efuse_api.o (from ['D:\\\\codedeveloper\\\\platformio\\\\packages\\\\framework-espidf\\\\components\\\\efuse\\\\src\\\\esp32\\\\esp_efuse_api.c'] and from ['D:\\\\codedeveloper\\\\platformio\\\\packages\\\\framework-espidf\\\\components\\\\efuse\\\\src\\\\esp_efuse_api.c'])
File \"D:\\codedeveloper\\platformio\\platforms\\espressif32\\builder\\frameworks\\\", line 609, in compile_source_files
========================= [FAILED] Took 932.51 seconds ========================="

This seems weird since they’re the same path. Hm no actually not. They are

  • D:\codedeveloper\.platformio\packages\framework-espidf\components\efuse\src\esp32\esp_efuse_api.c
  • D:\codedeveloper\.platformio\packages\framework-espidf\components\efuse\src\esp_efuse_api.c

Which is weird.

Does this behavior persist when you do the “General -> Clean” project task and then rebuild?

Does compiling a project for an Arduino Uno with the blink sketch work fine?