-
|
On macOS Sequoia 15.2 arm64, using lipo to thin the fat binary to arm64 creates an unopenable app.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
This breaks the code signing and notarization. You cannot do this unless you build from source or sign yourself. |
Beta Was this translation helpful? Give feedback.
-
|
I believe it's possible to sign both architectures individually, isn't it? This is the first app I've installed on my Mac that has been broken via thinning by lipo. |
Beta Was this translation helpful? Give feedback.
-
|
I'm unsure actually. I thought the notarization would apply to the full app bundle and not just the binaries themselves. If you can find a way to fix this I'd be happy to incorporate it into the release scripts! See this: https://github.com/ghostty-org/ghostty/blob/main/.github/workflows/release-tag.yml |
Beta Was this translation helpful? Give feedback.
-
|
I believe the method is to codesign the two binaries before they are merged via lipo. I am not sure off the top of my head. I can maybe get around to trying soon |
Beta Was this translation helpful? Give feedback.
-
|
FWIW I can confirm thinning by lipo should not break the app, I've done it many times on third party apps. |
Beta Was this translation helpful? Give feedback.
This breaks the code signing and notarization. You cannot do this unless you build from source or sign yourself.