-
Notifications
You must be signed in to change notification settings - Fork 9
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
build on M1 Mac running Monterey? #14
Comments
Ugh. I'm going to be honest I have no idea. This is a very hacked together thing for me as I don't really know Obj-C, Xcode, etc. I did just spend the day hacking version 0.3.0 in swift. I'm going to push it shortly and hopefully it works? |
Thanks @tgray - it worked! 🚀 2 small things:
|
Oh boy. I do not have an M1 Mac, and from my brief poking around, it sounds like it might be something to do with M1 Macs. Like this. If you could try a few things for me:
Feel free to paste in input with emails, etc. removed. As to the no argument error, I'll fix that. |
0.3.1 looking good. Still get the Running it with an arg works fine, search works & does not print the XXX. |
Glad to hear. It might be something in the argument parser library or maybe just something with swift package manager. I don't do much heavy lifting with the argument library so maybe I'll play around with removing it completely. |
Yeah I looked at the code too, don't really see anything that would cause it but I did find this: swift - allocating EKEventStore throws warnings - Stack Overflow So I guess one of those libraries may be leveraging EventKit under the hood, and someone at Apple left a debug message behind. Might be worth filing a bugreport, but maybe someone can test it on 12.3 to see if it's already fixed. |
Hi @tgray & thanks for releasing 0.2.2
I was eager to give it a try, but the build failed... Xcode 13.2.1 / macOS 12.2.1
The text was updated successfully, but these errors were encountered: