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

Flag: output path #131

Closed
steveklabnik opened this issue Aug 10, 2017 · 5 comments
Closed

Flag: output path #131

steveklabnik opened this issue Aug 10, 2017 · 5 comments

Comments

@steveklabnik
Copy link
Owner

This issue is part of #125

-o/--output: output path

Using this flag looks like this:

$ rustdoc src/lib.rs -o target\\doc
$ rustdoc src/lib.rs --output target\\doc

By default, rustdoc's output appears in a directory named doc in
the current working directory. With this flag, it will place all output
into the directory you specify.


Should we keep this flag or not?

@steveklabnik
Copy link
Owner Author

This seems important to keep.

Our default is different than this one; we assume Cargo and write to target/doc. Today's Cargo passes this flag to rustdoc to write to that location, and rustdoc defaults to ./doc.

@euclio
Copy link
Contributor

euclio commented Aug 25, 2017

Looks like -o is already claimed by rustdoc build --open.

@mgattozzi
Copy link
Contributor

Maybe just leave --open as a long flag only and have -o/--output be the other flags? Conventionally for many compilers and programs -o is used for output directories

@steveklabnik
Copy link
Owner Author

Yes, we should leave --open as a long flag only, and take -o for this.

hjr3 added a commit to hjr3/rustdoc that referenced this issue Dec 3, 2017
@hjr3
Copy link
Contributor

hjr3 commented Dec 3, 2017

There is some inconsistency with manifest-path having -path and --output not having -path. Also, #133 specifies --library-path.

steveklabnik pushed a commit to hjr3/rustdoc that referenced this issue Dec 31, 2017
steveklabnik pushed a commit to hjr3/rustdoc that referenced this issue Dec 31, 2017
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

4 participants