-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat: adding pkgs support for cross-compilation #161
base: master
Are you sure you want to change the base?
Conversation
@@ -30,6 +30,7 @@ in | |||
, clang-unwrapped ? defaultClangUnwrapped | |||
, stdenv ? defaultStdenv | |||
, isLintShell ? false | |||
, craneArgs ? { } |
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.
Is this really needed? I thought we'd just modify mergeArgs
to scan through buildInputs
and buildNativeInputs
and apply pkgs
over functions there.
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.
I did try the mergeArgs
route but it was a pain passing the buildInputs
and nativeBuildInputs
across different targets.
Resolving the packages as early as possible to pass it directly to mkFenixToolchain
ended up working smoothly
We'll need tests in ./checks that make sure it works. But right now that |
Got it, thanks for the review. I did not manage to get |
Hey @dpc, coming back to this PR
Tell me if there are still blockers to merge this |
closes #160.
This should not introduce any breaking changes, we can now pass a
buildInputs
andnativeBuildInputs
lambda tocraneMultiBuild
that we get resolved inmkStdToolchains
and ultimately passed tocraneLib
inmkFenixToolchain
.EDIT: I just realized my new commits were also forwarded to this PR, they basically add new targets (linux musl variants + windows64 with mingw).