go: propagate the apple sdk

[zowoq]

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[emilazy]

It might be best to hold off on this for now unless there's a pressing need, as the upcoming SDK rework is likely to change this interface again (to something much simpler, thankfully).

[reckenrode]

To add some detail and background: overrideSDK was added at literally the last minute to 23.11. I had to add it during the final staging-next cycle to fix curl because otherwise it was going to break things propagating frameworks. That version was incomplete. I improved it for 24.05, but I realized during that work it would not be possible to implement it generally. In particular, anything that is a dependency but not an input is invisible to it (e.g., in a hook or a file or a string).

The Darwin refactor will turn the SDK into a normal package. If you need the 11.x SDK, you add apple-sdk_11 as a build input. If your package exposes the SDK as part of its public API, you can propagate it. This will all work as expected for a normal package. If you need to set the deployment target, you will be able to use darwinDeploymentTargetHook to do that.

Another aspect of this is I am reworking how SDKs are built. I have the 10.12 through 14.4 SDKs in my WIP branch. They all build, and they all have source-based components. There’s not going to be a difference in SDKs between Darwin platforms other than what’s available. xcrun will also be available in the stdenv, pointing the nixpkg SDK and binaries.

I have a very WIP branch available at https://github.com/reckenrode/nixpkgs/tree/darwin-sdk-refactor. It’s very messy (because I’m using an adapter right now to avoid stdenv bootstraps), but the core of it works. I have successfully built Wine, MoltenVK, RPM, xcbuild, and btop with appropriate SDKs. It’s very unlikely this will land for the next staging-next cycle (because I still have to sort out bootstrapping the stdenv), but it may the one after that, and it will definitely be in 24.11.

[reckenrode]

The new SDK stuff is at #346043. For Go’s purpose, you’ll want to propagate the minimum SDK and deployment target like I did for Swift in #346947.

[reckenrode]

If you don’t mind, I added this PR to the follow up tracking list at #346043.

[zowoq]

@ofborg eval

[emilazy]

@ofborg eval

[emilazy]

Not sure why ofborg won’t eval. Can you try rebasing this on the latest staging to kick it into gear?

[zowoq]

Not much point waiting for ofborg, the eval queue is ~90.

[nixos-discourse]

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/title-the-darwin-sdks-have-been-updated/55295/1