Library Manager - Install to Local Project Wrong Location

[mriksman]

Hi,

First time user of PlatformIO. Off to a rocky start. Installed PlatformIO/VSCode and Python 3.8.2.

To get a feel for the software, I am looking at Library Manager and the lib_deps in Platform.ini.

Library Manager - Global; installs to C:\Users\{username}\.platformio\lib\{libraryname}
Using lib_deps in Platform.ini; installs to {projectname}\.pio\libdeps\esp01_1m\{libraryname}
Using the command line platformio lib install {libraryname} installs to {projectname}\.pio\libdeps\esp01_1m\{libraryname}

But the real confusing one is using
Library Manager - PROJECT LOCAL; installs to C:\Users\{username}\.platformio\penv\Scripts\.pio\libdeps\esp01_1m\{libraryname}

Which doesn't seem right...

[pfeerick]

I can confirm this, and this now explains what I had seen before (the install of a library to a project via PIO Home not working) On linux, I did an PIO Home -> Libraries -> Install to... of a library (OneWire in this instance) to an open project, and it installed the library to ~/.platformio/penv/bin/.pio/libdeps/pro16MHzatmega328/OneWire_ID1 ... although the project directory is actually /media/2TB_upper/Projects/PlatformIO/atmelAvr/7SegmentClock and pro16MHzatmega328 is the name of that particular env. No fancy symbolic links or anything to confuse PIO.

[pfeerick]

Related issue, which I posted against pio-home thinking it was more likely a fault in that module, rather than in the VSCode IDE extension... platformio/platformio-home#374

[ivankravets]

Duplicate of platformio/platformio-home#374