-
Notifications
You must be signed in to change notification settings - Fork 32
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
Add Universal Mac OS build #770
Comments
Sgtm, but:
Good news is that this is pretty simple to do in userland: universal binary can be created by gluing amd64 and arm64 binaries together. I think doing this in this repo makes sense, this way NPM release could default to universal binary + provide a way to override and use platform-specific one, if size is important. How to add this fake build target?
If someone contributes a PR, I can block some time for reviews. |
2023-05-18 maintainer conversation: Brave went down the path of using separate binaries (since they want to minimize the amount they are bundling/distributing) and we expect IPFS desktop to use separate binaries. We're not seeing the need currently. The "wrapper app" (Brave, desktop, Electron in the original post) can bring in both binaries. We're not sure if https://github.com/ipfs/npm-go-ipfs/ is smart enough to detect arm, but if that's the case, that should be in an issue in that repo. The biggest value we could see in completing this is to have a single "download for MacOS" URL at https://dist.ipfs.tech/#kubo. It has so-far worked though for users to select the right platform for themseleves. As a result, we're not planning to fix this. Please feel free to reopen if there are important usecases we're not accounting for. |
Hello, we'd like to bundle Kubo with Electron applications to run on Mac OS with Apple Silicone / x64 macs via the npm-go-ipfs module for the WebRecorder and Agregore Browser projects.
At the moment this is complicated by the fact that while Electron supports generating Universal builds for Mac OS, kubo currently requires choosing one or the other.
Would it be possible to add Universal Mac OS builds to the distribution matrix to enable this use case?
The text was updated successfully, but these errors were encountered: