-
-
Notifications
You must be signed in to change notification settings - Fork 708
[esp-idf] Failed build because “Multiple ways to build the same target were specified…” #515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @Honza0297 ! Could you please put together a minimal example to reproduce the issue? |
Certainly, however, during the preparation of the minimal example, I managed to build the project, with absolutely no change of anything. After I cleaned the project (General -> Clean), I am now unable to build it again. I'll dig deeper what changed (something had to) and provide you additional info. |
I somehow forgot to provide version info etc, may be helpful: Anyway, I found out what causes the error. My home directory (/home/jaberan) is a symlink to /var/home/jaberan. Sometimes, Platformio/cmake detects my $HOME prefix (or how to call that) as a /home (does not work), sometimes as a /var/home (works). The difference is present in CMakeFIles folder located in .pio/build/esp32dev. |
Update: After a little experimenting, I found out I can avoid the error by setting $HOME to "/var/home/jaberan" instead of "/home/jaberan". Then, I am able to create and compile working application. Not sure why PlatformIO (or esp-idf?) doesn't like my simlinked home... |
This bug is also easily reproducable in a Windows portable environment:
After having downloaded everything, the project wizard fails with that error:
Cleaning the project and rebuilding doesn't help. The same error rises after "Reading CMake configuration..." However, it's working when you do the steps above omitting PLATFORMIO_CORE_DIR and let install everything in the user's homedirectory. Of course, on AD enabled machines with folder redirection, this is not an option. VSCode:1.64.2 Regards, |
This issue has been automatically marked as stale because it has not had recent activity. Please provide more details or it will be closed if no further activity occurs. Thank you for your contributions. |
Same here. My home dir is a symlink to another directory on another ext4 partition, and I had to set $HOME to the symlink target in order to solve the issue. |
I am having a similar issue as described here, my .platformio dir is a symlink to another OSX account. I cannot set my home directory to the symlink target as I don't want to affect other things. |
Same problem here with a symlinked |
In case you are using the Flatpak version of VS Code on Fedora Silverblue or Kinoite, run the following command and restart VS Code: flatpak override --user "--env=HOME=/var/home/$USER" com.visualstudio.code This builds upon the discovery of @Honza0297 that PlatformIO apparently doesn't like symlinked home directories:
|
Hello!
When trying to build my project with esp-idf framework with PlatformIO IDE plugin in VSCode, the build fails as shown below:
What I have tried:
Do somebody know what could be the culprit of that and how to solve that? Thanks in advance!
The text was updated successfully, but these errors were encountered: