Difference in behaviour of `include_str` in a workspace

Question

Difference in behaviour of `include_str` in a workspace

tilpner opened this issue 5 years ago · 3 comments

This project compiles with cargo build, but not with crate2nix.

Including files from the same workspace but not the same crate is probably a niche feature (if it even is feature! I don't know if this is intentionally allowed by cargo, or was just forgotten to forbid).

I would understand a choice not to support this, but I brought it up anyway in case you want to fix all differences from the build process of cargo.

Answer 1 · 2019-08-24T19:48:06.000Z

I'll think about this. Thank you for reporting it and the test case!

Answer 2 · 2020-01-26T11:29:20.000Z

I closed this as I consider this WAI.

Answer 3 · 2024-03-18T11:29:35.000Z

@kolloch How can you workaround this limitation, if you have shared files in a workspace (E.g schemas)?