QUESTION: Using relative paths without blog_os workspace

[4e554c4c]

Hello, I am trying to work on crates that are used in blog_os such as multiboot2 which require me to use a relative path (or relative git repository). When I try to compile blog_os I get this error message:

error: workspace member `.../multiboot2-elf64/Cargo.toml` is not hierarchically below the workspace root `.../blog_os/Cargo.toml`

Is there any way to have a dependancy as a relative path without having it in the blog_os workspace?

[phil-opp]

Hmm, good question… The RFC says:

a crate which specifies [workspace] without a members key will transitively crawl path dependencies to fill in this key. This way all path dependencies (and recursively their own path dependencies) will inherently become the default value for workspace.members.

I don't think that this is a good default. A better default might be “all path dependencies below the workspace root”. I would recommend to open an issue at rust-lang/cargo.

Possible workarounds (untested):

• specify the workspace members explicitely:

[workspace]
members = ["crate1", "crate2", "crate3"]

• use .cargo/config` overrides

[4e554c4c]

Possible workaround number 1 does not work, I have tried it before opening this issue.

Possible workaround number 2 works perfectly, thank you for finding this.

[phil-opp]

Possible workaround number 2 works perfectly,

Great!

Possible workaround number 1 does not work

Sounds like a bug to me. Did you open a cargo issue?

[4e554c4c]

@phil-opp The relavent issue is rust-lang/cargo#3156 if you did not get a notification from me opening it