Don't use relative path includes for other crates...
brandon-reinhart opened this issue · 2 comments
brandon-reinhart commented
Might be worth re-organizing your projects to not use a relative paths to each crate. This makes it hard to reproduce a dev environment to make contributions!
Zeenobit commented
I've seen other projects (such as Bevy) do this pattern:
https://github.com/bevyengine/bevy/blob/main/crates/bevy_asset/Cargo.toml
bevy_ecs = { path = "../bevy_ecs", version = "0.14.0-dev" }
This is the same pattern I copied in Moonshine. I'm not sure if there is a more correct way to do this while still allowing me to develop the larger Moonshine project locally.
I'm open to suggestions!