-
Notifications
You must be signed in to change notification settings - Fork 3
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
Integrate MacOS DMG and Mac App Store builds into Nix Build Pipeline #10
Comments
Also we have manual code signing that we have to do. How to integrate this? I'm not sure of the workflow. @gideonairex can you describe it? |
After some experimenting, this is what we've found. the I have tried adding Attempting to
As a result, for now in the source, we will not include |
This requires some upstream fix then: svanderburg/node2nix#229. For now, anytime we have this situation, either we repackage that as Nix dependency if it provides an executable, or we just have to interactively do it with |
This is also related to the integration of macOS CI/CD MatrixAI/Polykey#4 |
This might be worth exploring: #16 (comment) Also we did do some overrides of Nix and NPM packages here: https://gitlab.com/MatrixAI/Engineering/nixpkgs-overlay/-/merge_requests/15. This shows you how to override the node packages structure in Nixpkgs upstream. And therefore how to apply an override at the end. There's definitely a way to ignore certain dependencies once we have generated them. But we will wait until we have MacOS CI/CD available before experimenting on this. We'll need to consider the usage of our application key and a manual Q&A process for our Mac applications. |
These can only be done on MacOS.
Can it work if Nix is running on MacOS? Need to experiment with this on Mac system. We have the M1 mac system to test on and also Mac systems that @gideonairex is running on.
If it works, we can at least have a consistent platform to work on, using Nix on NixOS and using Nix on MacOS.
However I have heard from @rbellec that Nix has some problems with the latest OS BigSur. So we should probably avoid that.
The text was updated successfully, but these errors were encountered: