-
Notifications
You must be signed in to change notification settings - Fork 89
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
Symlinks are not resolved after a submodule is cloned #230
Comments
Hi 🙂 Could you try using naersk from #167? Something like that should work: inputs = {
# ...
naersk.url = "github:nix-community/naersk?rev=bd4822e754eba04977667ab8a9e5314ae126cc1c";
}; ... or: inputs = {
# ...
naersk.url = "github:nix-community/naersk/bd4822e754eba04977667ab8a9e5314ae126cc1c";
}; |
Hmm.. it fails the same way.
Pretty much at the latest commit for that dependency. inputs = {
# ...
naersk.url = "github:nix-community/naersk?rev=bd4822e754eba04977667ab8a9e5314ae126cc1c";
};
# Output
packages.foo = naersk-lib.buildPackage {
pname = "foo";
root = ./.;
gitSubmodules = true;
}; Am I using it right? |
Yeah, looks right; well, thanks for the report, then - I'll try investigating it 🙂 |
Ah, the issue is that this file is a symlink, and we seem not to be resolving them (so after copying the dependency to |
Ahhh okay, that makes sense. Thanks for taking the time to give this a look! |
Ok, so it turns out submodules aren't relevant in this case. The problem is just that symlinks don't get resolved. Are there any pointers for how to start with this problem? I'd like to open a PR but I'm not too experienced with Nix. |
Hi 🙂 Unfortunately I didn't have time yet to investigate this issue more thoroughly, so I don't have any tips - I'll try taking a look some time next week and we'll see. Btw, I loved your article on creating static binaries! |
I see, I'll try to look into it to see if I can do anything. Thank you 😄. |
Heyah. Thanks for the awesome work!
I have a cargo dependency that contains a submodule, and it doesn't seem like it gets cloned properly by (I think).
Dep's submodule: https://github.com/lambda-fairy/maud/blob/main/maud_macros/src/escape.rs
nix version: 2.5.1
flake.nix
:nix build
log:The strange part is that running
cargo build
directly builds it just fine. I tried looking around the issues, and it doesn't seem like any of the ones I found are exactly this problem. Any pointers are appreciated!The text was updated successfully, but these errors were encountered: