-
Notifications
You must be signed in to change notification settings - Fork 182
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 for Apple Silicon #515
Comments
Anyone looking for a universal binary is welcome to test out my fork. Just put up a universal build: https://github.com/crash0verride11/ControlPlane/releases/tag/Monterey_v0.2_Universal I run Intel, so I can't test at all, but it is a universal build. Probably broken items, but what I use works fine. Added dark mode, though the menubar icon seems to change only occasionally (works fine running in Xcode, but not from a build). Not going to be putting a ton of work into the fork, but others are welcome to contribute. |
@crash0verride11, I tried running this in Xcode and there are a few frameworks that don't have arm64 support. I'm in no way an objective-c developer, so perhaps it's an easy fix. I just really want ControlPlane back in my life :D |
Whoops, mix up on that upload. Please try again, same link. Also actually uploaded the build as "Monterey_v0.2.1.zip." |
Some educated guesses:
I hope that helps! |
the referenced build doesn't work for me on an M1; probably due to code signing. |
I did get the build to work, thank you. FYI, It's impossible to add a wlan rule on a recent system, because the code expects the bssid to always be available, and apple has decided they're now a privacy concern, so it's always nil. There may be a way to ask for it, but I have not found it yet. |
The context switch worked fine for me, but the shell script rules didn't seem to run. (Is there a log anywhere?) |
I got it working (latest available Intel build): |
Would you be so kind as to provide your Apple silicon build? Thanks in advance! |
Are you considering providing a universal binary in the near future?
The text was updated successfully, but these errors were encountered: