-
Notifications
You must be signed in to change notification settings - Fork 230
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
64-bit version for mojave / catalina users? #38
Comments
I don't know. Certainly the 32 bit version works on mojave right now. I've tried 4 different avenues so far (starting from scratch) from what I've read and attempted it seems like scriptbridge building has been been broken since mojave. I'm not running catalina myself. |
The 2.6 Mavericks version, is actually 64 bit. I didn't realize because I was actually running 2.5 on my own machine. I have no problem building the project on high sierra, which I still had access to a machine running. So now I'm seeing if I can build noterized. |
let me know if 3.0 works on Catalina! it's been notarized! |
Anything you have done others could repeat for iTerm and contribute as a fork? It would be good if the repo could keep hosting fully supported version for iTerm too.
Do the release notes mean that iTerm is now unsupported btw?
…Sent from my iPhone
On 9 Oct 2019, at 09:24, Jay Tuley ***@***.***> wrote:
let me know if 3.0 works on Catalina! it's been notarized!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@Panajev, yeah i struggled to get this work due to the new hardened entitlements situation, I never used iterm2 myself, back when I added iterm2 support it was easy, but now it’s quite a bit more complicate, If someone wants to continue on some where else that’s fine, but I’m not going to be releasing the Iterm version anymore. |
@jbtule can confirm it works fine with catalina and using ZSH. |
@YvesR thank you! 🙏 |
Is it possible to create a 64-bit version for mojave/catalina users?
The text was updated successfully, but these errors were encountered: