It used to, but these days there are pre-built executables which avoids the time consuming builds of those, but more importantly means a native compiler for Windows isn't required.I can't really make any predictions as to whether pioasm builds will work on windows
The pre-built executables are downloadable assets from https://github.com/raspberrypi/pico-sdk-tools/releases/
To use those; these lines need adding to the CMakeLists.txt' - but continue reading before doing so -
Code:
set(picotool_DIR $ENV{PICO_SDK_PATH}/../picotool)set(pioasm_DIR $ENV{PICO_SDK_PATH}/tools/pioasm)To avoid having to add those to every 'CMakeLists.txt' copied from a Pi, and allow continued use of 'cmake ..' on the command line, the pragmatic solution is to hack the '${PICO_SDK_PATH}/external/pico_sdk_import.cmake' file and add them to its end. Windows may require Notepad to be 'Run as Administrator' to allow that.
This is what I have at the bottom of my '${PICO_SDK_PATH}/external/pico_sdk_import.cmake' -
Code:
# .---------------------------------------------------------------.# | Set the pre-built tool paths for Windows - 32-bit or 64-bit |# |---------------------------------------------------------------|# |# |if(WIN32)# | set(picotool_DIR ${PICO_SDK_PATH}/../picotool)# | set(pioasm_DIR ${PICO_SDK_PATH}/tools/pioasm)# | message("Setting Windows pre-built tool paths ...")# | message(" picotool_DIR = ${picotool_DIR}")# | message(" pioasm_DIR = ${pioasm_DIR}")# |endif()# |# |# |# `---------------------------------------------------------------'Statistics: Posted by hippy — Sat Jul 26, 2025 10:52 am