steveklabnik/rustdoc

Flag: library path

Open

#133 opened on Aug 10, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees) (22 forks)github user discovery
E-Mediumbackendhelp wantedquestion

Repository metrics

Stars
 (104 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

This issue is part of https://github.com/steveklabnik/rustdoc/issues/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?

Contributor guide

Research direction
Research the history and usage of the ` library path` flag in rustdoc, compare with other Rust tools like rustc, and evaluate its necessity and alternatives such as automatic discovery or environment variables.
Tech stack
rust
Domain
devtoolsdocumentation
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustCommand line interface
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40