I have seen the maxgerhardt issue#9.
Compiling any project for the RP2040 on a Raspberry Pi is impossible since the compiler package is missing. For a Pi4 there is no toolchain for either armv7 or armv8, which is what you have for a RPi model 4 running in 32-bit or 64 bit.
Since there is a PR outstanding for this, I don't understand the comment on the original issue.
When the Pi models available didn't have the power to run VSCode and the platformio integration, I understand reluctance to accept community stuff relating to "minority" ports. However, it is possible for this to be fixed (or at least documented here!) so that the Raspberry Pi Pico platform (RP2040) can be supported out of the box.
If it was resolved, it would be possible to use the software the way the registry design was intended to work - one place to provide the platform, the framework, and the toolchains for devices.
I have seen the maxgerhardt issue#9. Compiling any project for the RP2040 on a Raspberry Pi is impossible since the compiler package is missing. For a Pi4 there is no toolchain for either armv7 or armv8, which is what you have for a RPi model 4 running in 32-bit or 64 bit.
Since there is a PR outstanding for this, I don't understand the comment on the original issue.
When the Pi models available didn't have the power to run VSCode and the platformio integration, I understand reluctance to accept community stuff relating to "minority" ports. However, it is possible for this to be fixed (or at least documented here!) so that the Raspberry Pi Pico platform (RP2040) can be supported out of the box. If it was resolved, it would be possible to use the software the way the registry design was intended to work - one place to provide the platform, the framework, and the toolchains for devices.