-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Make cross compilation of Nix itself easy using default.nix
#8561
Comments
…ir relation to Nix We don't rely on this terminology a lot, but when we do, we should refer to them through here because we need to add our own context. This will be useful for our hacking documentation and our documentation for [cross compiling nix] (TBD), but I haven't made any references to these terms yet, because another PR is already touching the text. [cross compiling nix]: NixOS#8561
default.nix
default.nix
Either this, or we decide that we only want a flake and admit that flakes through the nix CLI are not particularly conducive to flexible cross compilation yet. In that case we should refer people to Nixpkgs which has established patterns and reasonable (?) documentation for doing cross compilation of all its packages including |
In #7876 I proposed that we have separate Nixpkgs-style |
The alternative is to expose a function on the flake, but that would implicitly be public, but also inconvenient to use and not an interface we'd want to keep. So yes, it would be nice to do #7876 first. |
We could make cross compilation a lot easier using
default.nix
, as it can take the systems as parametersOriginally posted by @roberth in #8556 (comment)
The text was updated successfully, but these errors were encountered: