Don't much care. The zipped examples I provided compile with it in, both on the Pi command line and under VS Code using 'CMake Tools'.That's it:
remove set(PICO_SDK_PATH $ENV{PICO_SDK_PATH})
Happy?
And the OP's issue seemed to be that the Extension wouldn't offer a compile option when there isn't a 'pico_sdk_init' in 'CMakeLists.txt'.
I'm not sure how removing that line would solve that problem..
Even if removing that line allows the VS Code Pico Extension to build, it then breaks both the command line and VS Code 'Cake Tools' builds when starting with an empty build directory.
Anyone know a good CMake conditional which can indicate when running under the VS Code Pico Extension or not ?
That should also wrap what the Extension adds to the 'CMakeLists.txt' or it also creates a breakage. Maybe someone could raise an issue for that ?
And not specifying a pin value for 'PICO_DEFAULT_PIO_USB_VBUSEN_PIN' appears to have that default to GPIO1 which may not be expected nor desirable given that's also UART0 RX.
Statistics: Posted by hippy — Fri Feb 20, 2026 2:16 am