Open sgeos opened 1 year ago
I'd imagined you'd use crankstart as a dependency from crates, so this would not be an issue.
What are you trying to do where you want to include crankstart in your workspace?
I guess I wanted to put crankstart in the workspace because the instructions for using it include the following entries in Cargo.toml.
[dependencies]
crankstart = { path = "../crankstart" }
crankstart-sys = { path = "../crankstart/crankstart-sys" }
Dropping crankstart into the workspace would allow the above path to be used as is. At the time, crankstart and my project workspace were in completely different directories. Since I have a bunch of different things in my workspace, adding crankstart to the mix did not seem unreasonable. The directory structure is a lot like the one in my original post, only there are two libraries.
Not unreasonable, but I favor leaving it as-it in expectation that it might eventually end up being published to crates.io.
Are there plans to publish to crates.io?
Nothing more solid than an expectation.
Would you be open to help? I would love to assist.
crankstart is workspace with one member. It cannot, therefore, be included in another Rust workspace as a git submodule. The workaround is to install crankstart and the user workspace in the same directory.
ideal directory structure
workaround directory structure
EDIT: Another workaround is probably to include crankstart as a git submodule and exclude it from the user workspace.