Dep info contains invalid file paths when rustc-macro is used #36625
Comments
53 tasks
|
Added this to the macros 1.1 tracking issue #35900 (I consider this a blocker for stabilization) |
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Sep 27, 2016
This "special filename" is surrounded by `<>` to ensure that `FileMap::is_real_file` returns `false`. This way the "files" parsed here aren't emitted as dep info `.d` files and don't confuse Cargo about non-existent files. Closes rust-lang#36625
bors
added a commit
that referenced
this issue
Sep 28, 2016
rustc: Use a special filename for macros 1.1 This "special filename" is surrounded by `<>` to ensure that `FileMap::is_real_file` returns `false`. This way the "files" parsed here aren't emitted as dep info `.d` files and don't confuse Cargo about non-existent files. Closes #36625
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Noticed it causing issues with cargo as it uses
--emit=dep-info,linkand then parses the files as part of the fingerprinting process.It seems every instance of macro generated code (e.g. via serde_derive) creates a
rustc-macro\ source\ codeentry into this file which when cargo tries to look up it can't find.Cargo issue: rust-lang/cargo#3094
The text was updated successfully, but these errors were encountered: