But what about people who prefer the command line, are developing via SSH on headless systems, or are using other IDE to do their development ?The roadmap here is to stop using the Windows Installer (hence the past tense), and recommend using the VS Code extension for getting started with Pico development across Windows, MacOS and Linux. It then provides a standard interface for Pico development across all platforms.What is the road map here, to update the Official Pico SDK Installer to be the same as whatever you are doing for VS Code, or what ?
Apart from some disappointing inconsistency in naming I don't have much complaint about what we currently have using the official installer -
I have that working to build code within the Raspberry Pi provided Start Menu links, without those, from the standard Command Prompt, within VS Code launched from the desktop, in Notepad++, in Geany.PICO_SDK_PATH=C:\Program Files\Raspberry Pi\Pico SDK v1.5.1\pico-sdk
PICO_EXTRAS_PATH=C:\Users\User\Documents\Pico-v1.5.1\pico-extras
Do you have any data for what percentage of users, Linux, Mac and Windows, use VS Code, the command line, or other IDE ?
I guess if you are going down the VS Code path that's fair enough. Those of us who don't want that will simply be back to where we were before the rather excellent 1.5.x installers appeared, will just have to sort ourselves out.
Statistics: Posted by hippy — Fri Aug 02, 2024 6:58 pm