Link errors on darwin caused by darwin.CF

veprbl · February 13, 2022, 9:36am

Yes, a setup hook

NixOS/nixpkgs/blob/8436842aaf7f3b6bbe7fe2d755ab0d6cc75155bf/pkgs/os-specific/darwin/apple-sdk/cf-setup-hook.sh

linkSystemCoreFoundationFramework() {
  NIX_CFLAGS_COMPILE="-F@out@/Library/Frameworks${NIX_CFLAGS_COMPILE:+ }${NIX_CFLAGS_COMPILE-}"
  # gross! many symbols (such as _OBJC_CLASS_$_NSArray) are defined in system CF, but not
  # in the opensource release
  # if the package needs private headers, we assume they also want to link with system CF
  NIX_LDFLAGS+=" @out@/Library/Frameworks/CoreFoundation.framework/CoreFoundation"
}

preConfigureHooks+=(linkSystemCoreFoundationFramework)

is enabled when darwin.apple_sdk.frameworks.CoreFoundation is used

github.com

NixOS/nixpkgs/blob/8436842aaf7f3b6bbe7fe2d755ab0d6cc75155bf/pkgs/os-specific/darwin/apple-sdk/default.nix#L283-L285


      
          CoreFoundation = lib.overrideDerivation super.CoreFoundation (drv: {
            setupHook = ./cf-setup-hook.sh;
          });

It seems like Cocoa depends on AppKit, which depends on Foundation, which depends on CoreFoundation: https://github.com/NixOS/nixpkgs/blob/8436842aaf7f3b6bbe7fe2d755ab0d6cc75155bf/pkgs/os-specific/darwin/apple-sdk/frameworks.nix

It would appear that the cf-setup-hook.sh prepends the -F flag, so they should always come first. If that is not the case, it could be because of a bug. You could file an issue to Issues · NixOS/nixpkgs · GitHub. If you do, please, include a minimal reproducing example.