You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
leo60228 opened this issue
Jul 24, 2019
· 2 comments
Labels
A-crossArea: Cross compilationA-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)C-bugCategory: This is a bug.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.
If a target is explicitly specified on the command line, even if it is the same target as the host, then proc macro crates will not be documented by cargo doc --all. When a cargo configuration file is used to set a default target for cross-compliation, this can prevent documenting proc macro crates at all.
The text was updated successfully, but these errors were encountered:
jonas-schievink
added
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
C-bug
Category: This is a bug.
A-cross
Area: Cross compilation
labels
Aug 6, 2019
A-crossArea: Cross compilationA-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)C-bugCategory: This is a bug.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.
If a target is explicitly specified on the command line, even if it is the same target as the host, then proc macro crates will not be documented by
cargo doc --all
. When a cargo configuration file is used to set a default target for cross-compliation, this can prevent documenting proc macro crates at all.Minimal testcase: https://github.com/leo60228/minimal_testcase
The text was updated successfully, but these errors were encountered: