-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
darwin packages: Get ready for cross #122527
darwin packages: Get ready for cross #122527
Conversation
pkgs/os-specific/darwin/apple-source-releases/configd/default.nix
Outdated
Show resolved
Hide resolved
callPackage = self.newScope { inherit appleDerivation; }; | ||
appleDerivation' = stdenv: appleDerivation'' stdenv pname version sdkName sha256; | ||
appleDerivation = appleDerivation' stdenv; | ||
callPackage = self.newScope { inherit appleDerivation' appleDerivation; }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about appleDerivationNoCC
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well appleDerivation'
takes an arbitrary stdenv
. I think I would like that to just replace appleDerivation
eventually.
pkgs/os-specific/darwin/apple-source-releases/libresolv/default.nix
Outdated
Show resolved
Hide resolved
Does this allow to cross-compile darwin on Linux? |
f013127
to
d4a63a9
Compare
@Mic92 No, but I believe it is "getting the mass rebuilds out of the way". I have another commit with an actual attempt at that which I think might work better after @thefloweringash's darwin -> darwin attempt. |
If things build fine with `stdenvNoCC`, let them use that. If tools might be prefixed, prepare for that, either by directly splicing or just using the env vars provided by the wrapper setup-hooks. Co-authored-by: Dmitry Kalinkin <[email protected]>
d4a63a9
to
7bba32a
Compare
Rebuilt darwin stdenv and hello just to double check. |
Motivation for this change
If things build fine with
stdenvNoCC
, let them use that. If toolsmight be prefixed, prepare for that.
This is a mass rebuild, but I don't think the final stdenv should be any different in contents, so I think it's safe.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)