@ivankravets Its been awhile but im now back to a bit of programming and loving the progress of PIO. Good work. I am very taken by VSCode and it is potentially a game changer for me, but I find this problem frustrating. I have been trying for days now to fix it. It is a common problem but the VSCode people always point to the extension being the culprit. I had found an issue somewhere ( and have just searched for it for 30mins and cannot find it ) where you said that this is due to .ino file being used and not a .cpp file. I am using a .cpp file here and I still get it.
I am using
VSCode - Version: 1.51.1
PIO - PlatformIO 5.0.3
PIO IDE - v2.2.1
If I build a project with a lib symlinked in the ./lib folder I get the following error when I click on a compile “problem”
If I make a copy of the whole library, in this case ESPManager, and place it in a folder which I then add to platform.ini as a lib_extra_dirs I get exactly the same error.
If I then copy the actual directory to the ./lib folder in project root then it works as expected.
Looking at the error message it is resolving the path incorrectly by adding
/Users/amelvin/git/MySONOFF
with
/Users/amelvin/git/PangolinMQTT/src/PANGO.cpp
when the first part is the project root and the second part is the full path of the symbolic or extra_dirs lib.
This is essentially a fresh install, VSCode + PIO IDE… and nothing else.
Any ideas would be appreciated.
