Building crate that has a git submodule that is a crate that one depends on as a path dependency seems to fail? about naersk HOT 4 CLOSED

Could you try passing gitSubmodules = true; to buildPackage? 👀

from naersk.

I think I am already doing it. Check the example repository?

from naersk.

Ah, right - I didn't see that on the phone 😅

So, in this case you're actually hitting a limitation of Nix:
NixOS/nix#6633
... where doing src = ./.; causes Nix to present the source directory to Naersk without the submodules.

This can be worked around by doing:

defaultPackage = naersk-lib.buildPackage {
  src = self; # voilà
};

... committing all the changes (so that you have a clean Git tree, it's important) and then running:

nix build '.?submodules=1'

I think there's nothing Naersk could do on its side to overcome this issue, since we just read the src directory Nix prepares and there's no way to tell Nix to force-initialize-submodules from within Nix code.

Fortunately, there's a pull request to improve this:
NixOS/nix#7862

from naersk.

I was able to get around this by removing the submodule and instead using cargo to fetch the dependency for me. Thanks for looking into this!

from naersk.