Using `pest_derive` without `std` under a workspace fails in Windows.

[Shaddy]

Using `pest_derive` without `std` under a workspace fails in Windows.

[tomtau]

I wonder why that would be: is it this https://superuser.com/questions/1069055/what-is-the-function-of-question-marks-in-file-system-paths-in-windows-registry ?

I have seen the ?\C:... path used a lot to get access to files/paths longer than 260 characters. At least when dealing with Win32 API calls. (...)

It could also be a bug in Cargo / Rust tooling in how it populates those env vars on Windows?

[tomtau]

rust-lang/cargo#9770

[tomtau]

Maybe a proper fix is to use something like normpath: wasmCloud/wasmCloud@8b876f1 ?

[tomtau]

or call canonicalize on env!("CARGO_MANIFEST_DIR") and then use .push(es) to construct the path?

[Shaddy]

or call canonicalize on env!("CARGO_MANIFEST_DIR") and then use .push(es) to construct the path?

I tried with canonicalize but it has the same problem, as soon as you enter relative path with the prefix "canonicalize" it simply does not find the file. And if the prefix is already there, it won't be removed.

I also don't understand that if I create a simple project with a build.rs and load the CARGO_MANIFEST_DIR path is not prepended with \\?\, but that's another story (tested just in case, if was because the Cargo.toml rustc version but it seems only happens when running from a different directory).

normpath sounds like the best approach probably at this moment