Nikhil Dabas

Interestingly, `$PSCmdlet` seems to be available when calling functions defined inside the script called by `iex`. It's just the top-level code that doesn't get `$PSCmdlet` because it is essentially dot-sourced...

If you're just looking to compile picotool on Windows without the overhead of Visual Studio or WSL, MSYS2 works fine with no changes, like [we've done for pico-setup-windows](https://github.com/raspberrypi/pico-setup-windows/blob/master/packages/picotool/build-picotool.sh).

It's basically impossible for anything in user-mode code to trigger a blue screen on Windows. So I'd say it's not anything If you are consistently getting a blue screen on...

Regarding testing, GitHub Actions might be worth considering, because they give us access to Windows, Ubuntu, and macOS hosts, and all for free -- plus, the testing can be fully...

> This is all a bit more work than I meant to do, but I think it's a good cause and will make a difference to people. Probably a good...

Perhaps we can use this for testing on macOS? At least for a quick smoke test? https://github.com/sickcodes/Docker-OSX/

> > this PR only skips the git clone bit if the picoprobe/picotool directory exists, but will still try to build those even if they exist. > > Hmmm, if...

@lurch I had a go at adding in `git pull --ff-only`, and that would require some minor changes to the conditional parts of the script. Can we merge in #14...

I think the entire repo has been superseded by #20 😀 I haven't tested that myself, but yes, if that PR is merged, this should be closed.

This should really not happen after a successful install -- are all of the tools present and installed into `C:\Program Files\Raspberry Pi\Pico SDK v1.5.0`? You should have folders like `cmake`,...