Windows 11 Not supported (possible on an ARM install only) about pico-setup-windows HOT 9 CLOSED

The installer works under Windows 11 on an x86 system, so this is an Arm-only problem.

Although, that said. If you have an Arm-based Mac, why are you attempting to install the toolchain under Windows running in Parallels? Why not just install it under macOS?

The instructions for installation on Mac (both Arm and x86) are documented in section 9.1 of the "Getting Started" guide and work out the box (I write the documentation, and my daily driver is a Mac, the Mac instructions are always going to work out of the box).

from pico-setup-windows.

Thanks for your reply.

I agree it is an Arm-only problem. It would still be a macOS problem (remember, this is all on an Apple Silicon machine (M2 in this case). But, that is a minor detail. The issue isn't the toolchain. Arm's Apple Silicon release works fine. The problem (for me) is understanding the various config files that VS Code requires. There are a number of YouTube videos that come close to a good explanation but not that completely (that I've seen) thoroughly explain the VS Code configuration files.

This project looked like a good opportunity to see a functioning install to understand VS Code. I could then use the knowledge gained and port over what I needed with some modifications.

from pico-setup-windows.

I am closing the issue as this is probably a tangent for the project, and a project dedicated for MacOS users would be a nice idea.

from pico-setup-windows.

…and a project dedicated for MacOS users would be a nice idea.

I'm am currently looking about for someone to work on a macOS installer. It'd probably be not much more than something like the pico-setup script for Raspberry Pi OS wrapped inside a PKG installer file.

from pico-setup-windows.

If you're just looking for the VS Code config, the config files in this project should work just fine. Just copy them into a .vscode directory in your project. The files assume that you have the toolchain installed, PICO_SDK_PATH configured, etc. which the pico-setup script linked to by @aallan does for you.

As for a complete macOS installer, I guess that would be the setup script, the VS Code config, and possibly pre-compiled versions of OpenOCD, picotool, pioasm, and elf2uf2.

from pico-setup-windows.

@ndabas Good suggestion. I will take a look at your suggestion and see how far it takes me.
@Aalan I have never written a dmg/pkg for the mac but have found a decent tutorial on how to do so. I will take a look and see if I am able to make progress with doing so. It makes take me a week or two (due to prior commitments). This is definitely needed for the macros community. Given that the ARM GNU toolchain is available for both the x86 and the Apple silicon, my approach would be to install the toolchain in the ~//opt or /opt (all users) directory and make that an option. I have no issues with a brew or other solution install, but I prefer a purist approach as I come from both a Windows/Linux/embedded developer background. I will get back to you in the next week or two to let you know my progress. It's possible someone may beat me to it, but that's OK. The goal is to create something that mac users can benefit from.

from pico-setup-windows.

Note, we are looking at a different solution to this for supporting the toolchain on MacOS. So if you do this, it may end up not being used, or at least

Basically, we'd prefer to install the toolchain through a VSCode extension, which would then make it possible to support Linux, MacOS and Windows all through the same mechanism... But we're still looking into it and don't know whether this will actually be the right solution...

from pico-setup-windows.

Understood. What exactly does installing through a VSCode extension entail? I was under the impression that the toolchain was installed in a location and VSCode references the toolchain by an environment variable? Thanks.

from pico-setup-windows.

Got it. I was not aware of the extensions brought up in this discussion. I am not a seasoned VS Code user (more IDE such as Segger, TI CC, or "Eclipse-based" tools. I'm struggling to wrap my mind around VS Code -particularly the settings files. So, I appreciate your input and understand the reasons for not going astray. I wrote that I did not see the Apple silicon support, just went back and see it. Thanks for the input. I am going to check that out before working on my next steps.

from pico-setup-windows.