hmmm - don’t understand that, pio was installed in user-home/.platformio
one thing I did after deleting the platforms folder in first reply was I tried the CLion plugin “home” command which did a bunch of stuff I didn’t expect including starting a local webserver - maybe that had something to do with my weird compiler output the second time.
Anyway - a complete delete and re-install seems to have done the trick - but the clion plugin still seems to need a bit extra to work
so for anyone else wanting the explicit steps :
delete pio installation
re-install via installer script (python get-platformio.py)
install platform ( pio platform install espressif8266)
uninstall clion pio plugin
install clion pio plugin
now for the extra bit :
start git bash client (for windows), change to your project directory and run " platformio init --ide clion"
May I ask why it is not supported to install PlatformIO in the global Python installation? This is the standard way Python packages are installed on most common Linux distributions, including mine (an Ubuntu derivative). Do you offer an alternative Debian package which could be installed in place of the one that is in the official repos?
I’ve only ever seen distributations try and package PlatformIO, but these quickly get outdated, as the PlatformIO core is updated rather often, and distributions are slow. Not seen any .deb redistribution of the PlatformIO made by PlatformIO staff yet – right @ivankravets?
Python’s PyPi does not manage dependencies in a way that npm does (installed sub-dependencies to the nested folders). As a result, 2 or more Python packages can conflict due to the different version requirements. For example, PlatformIO Core depends on Click >=8, whereas Debian/Ubuntu can potentially ship outdated Python packages that depend on Click 6. In this case, if PyPi upgrades click to the latest version, other systems packages will be broken.
The only solution to this is using Python virtual environments. You can create it manually, but we recommend using PlatformIO Core installer script that automatically does all works for you:
Creates a virtual environment in ~/.platformio/penv
Install PlatformIO Core dependencies into the isolated environments
You can later symlink ~/.platformio/penv/bin/pio to /usr/local/bin/pio.