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
{{ message }}
This repository has been archived by the owner on May 20, 2020. It is now read-only.
If your crate has dependencies, rustdoc needs to know where to find them.
Passing --library-path gives rustdoc a list of places to look for these
dependencies.
This flag takes any number of directories as its argument, and will use all of
them when searching.
Should we keep this flag or not?
The text was updated successfully, but these errors were encountered:
Similar to #135 (comment) I am not sure if --library-path is needed. cargo supports configuring library paths through build.rs, which rustdoc honors when generating the analysis.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue is part of #125
-L
/--library-path
:Using this flag looks like this:
If your crate has dependencies,
rustdoc
needs to know where to find them.Passing
--library-path
givesrustdoc
a list of places to look for thesedependencies.
This flag takes any number of directories as its argument, and will use all of
them when searching.
Should we keep this flag or not?
The text was updated successfully, but these errors were encountered: