Skip to content
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

Difference in behaviour of include_str in a workspace #17

Closed
tilpner opened this issue Aug 24, 2019 · 3 comments
Closed

Difference in behaviour of include_str in a workspace #17

tilpner opened this issue Aug 24, 2019 · 3 comments

Comments

@tilpner
Copy link
Contributor

tilpner commented Aug 24, 2019

Test case is here.

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.

@kolloch
Copy link
Collaborator

kolloch commented Aug 24, 2019

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

@kolloch
Copy link
Collaborator

kolloch commented Jan 26, 2020

I closed this as I consider this WAI.

@noverby
Copy link

noverby commented Mar 18, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants