Skip to content
This repository has been archived by the owner on May 20, 2020. It is now read-only.

Flag: library path #133

Open
steveklabnik opened this issue Aug 10, 2017 · 2 comments
Open

Flag: library path #133

steveklabnik opened this issue Aug 10, 2017 · 2 comments

Comments

@steveklabnik
Copy link
Owner

This issue is part of #125

-L/--library-path:

Using this flag looks like this:

$ rustdoc src/lib.rs -L target/debug/deps
$ rustdoc src/lib.rs --library-path target/debug/deps

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?

@steveklabnik
Copy link
Owner Author

steveklabnik commented Aug 10, 2017

This seems pretty important.

@hjr3 hjr3 mentioned this issue Dec 3, 2017
@hjr3
Copy link
Contributor

hjr3 commented Dec 5, 2017

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants