Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support macOS #19

Closed
michaelstoops opened this issue Apr 1, 2021 · 5 comments · May be fixed by #20
Closed

Support macOS #19

michaelstoops opened this issue Apr 1, 2021 · 5 comments · May be fixed by #20
Labels
wontfix This will not be worked on

Comments

@michaelstoops
Copy link

I wish this script supported macOS.

@aallan aallan added the wontfix This will not be worked on label Apr 1, 2021
@aallan
Copy link

aallan commented Apr 1, 2021

Our primary supported development platform for RP2040-based boards is the Raspberry Pi, running the latest version of RaspberryPi OS. However we support, and have instructions for manual installation on, both Windows 10 and macOS in the Getting Started guide.

There is a third-party installation script for Windows, which performs roughly the same sort of task as pico-setup. Personally I'd be happy to see a similar script for macOS support — it should be a lot simpler to write than the Windows script as macOS installation follows the Linux installation more-or-less step by step after the initial toolchain dependences are installed using brew. However this isn't something we'll be doing ourselves.

@aallan aallan closed this as completed Apr 1, 2021
@michaelstoops
Copy link
Author

However this isn't something we'll be doing ourselves.

If I wrote it, would you accept the pull request, or are you saying that you don't want to have any ownership over a more broadly-scoped tool?

@aallan
Copy link

aallan commented Apr 4, 2021

If I wrote it, would you accept the pull request, or are you saying that you don't want to have any ownership over a more broadly-scoped tool?

We wouldn't want to have ownership over a more broadly-scoped tool as we'd then have the responsibility for maintaining it.

@michaelstoops
Copy link
Author

That point of view makes sense, even though mine is a bit different.

Either way, I have submitted #20. If Raspberry Pi doesn't want ownership, I'll change the and license to what I would choose.

@aallan
Copy link

aallan commented Apr 6, 2021

We're chatting about it internally, #20 looks like a significant amount of work has been done.

@aallan aallan linked a pull request Apr 6, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants