can't use local crates in depedencies

[mirsella]

hello !

i want to use crabtime in a workspace setup, in crate A. but i need to use a type defined in crate B in the compile time macro.
but: crabtime::eval or crabtime::function with [build-dependencies] dont work with path or workspace dependencies as the build crate created by crabtime path is nested inside target.

Example repro: https://github.com/mirsella/crabtime-path-dep

possible solutions idea:

• allow #![dependency(anyhow = "1.0")] even in nightly and support more options,
  for example #![dependency(anyhow = { path = "../../../../b"})]
• auto convert the relative path in [build-dependencies] when creating the crate. probably the best solution ?

thanks !

[mirsella]

looking at the code { workspace = true } should be supported but its not actually working:

   Compiling eval_project v1.0.0 (/home/mirsella/dev/crabtime-repro/target/debug/build/crabtime/test)
error[E0433]: failed to resolve: use of unresolved module or unlinked crate `b`
   --> src/main.rs:195:25
    |
195 |                 let v = b :: B("Hello".to_string());
    |                         ^ use of unresolved module or unlinked crate `b`
    |
    = help: if you wanted to use a crate named `b`, use `cargo add b` to add it to your `Cargo.toml`

For more information about this error, try `rustc --explain E0433`.
error: could not compile `eval_project` (bin "eval_project") due to 1 previous error

[mirsella]

oh actually workspace = true only copy the workspace dep version if there is one. in my case where its a workspace member and not a crate on crates.io, it will not copy anything into the build project

[purpole]

Hello and first of all: Thank you very much for crabtime, it's awesome!

I stumbled upon the same issue today. Are there any plans to support relative path dependencies (I saw #46, but it looks stale?)? 🙂