-
If you comment/uncomment this line: you get different devShells (at least, the name of the devShell is different). I can understand that the project devShell is supposed to be the union of all the crate devShells contained within that project, but if you have that line commented out you get some kind of "default" devShell. Is the intention that nix-cargo-integration actually allows you to specify more than one project/workspace in a flake? If so, this is not clear from the simple-workspace example, as there doesn't seem to be any information in the flake.nix which ties my-crate and my-other-crate to my-project .
|
Beta Was this translation helpful? Give feedback.
Answered by
yusdacra
Apr 2, 2023
Replies: 1 comment
-
That was a bug, the "default" devshell appearing that is. I have fixed that in latest master. And yes, NCI does allow specifying multiple projects. A project can be a crate or a workspace. I can add an example showcasing that if it's not clear. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
yusdacra
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
That was a bug, the "default" devshell appearing that is. I have fixed that in latest master. And yes, NCI does allow specifying multiple projects. A project can be a crate or a workspace. I can add an example showcasing that if it's not clear.