New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo doc doesn't work on a project named rustdoc
#4283
Comments
|
This may be Windows-specific. On Linux I get "error: cannot document a package where a library and a binary have the same name", and if I work around that by setting a different name in a |
|
Ah sorry, I forgot that I didn't actually commit the [[bin]]
name = "rustdoc"
doc = falseline. Doing that now... So yeah, maybe a Windows thing. Oh, wait:
This is not what I did; can you try the |
|
|
|
This is probably because |
|
Ah ha! So yeah, that seems like a WONTFIX to me. Thanks! |
|
Would it be possible to fix this by appending the target directory to
|
|
Ah unfortunately not b/c the intention there is to prepend (e.g. libs in the target dir take priority). @steveklabnik I wouldn't necessarily say this is a WONTFIX, I think it's reasonable to detect the project's name is literally |
|
Cool, I wasn't sure if this was too niche to support or not! Should we do that unconditionally, regardless of platform, or also detect the |
|
Ideally I think we'd do it unconditionally, but it wouldn't be a "pretty" patch in the sense that where |
|
I personally can't reproduce this when checking out |
|
I am not developing that project anymore, so I don't know. You shouldn't need my specific checkout though. That being said, a new project named |
So uh,
gives
This is because
steveklabnik/rustdocdoes not yet support the--crate-nameflag. Why is it trying to use therustdocinside oftargetrather than the real one?Maybe this is a WONTFIX, but I figured I'd file it just in case.
The text was updated successfully, but these errors were encountered: