-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Build docs into a different directory #11860
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
Comments
We use the |
Could we enforce out-of-tree builds like servo does? |
@huonw We could, but servo only does it because the build system is so bad that an in-tree build causes havok. The docs are the only problem I'm aware of with ours. |
@alexcrichton Does the built docs actually depend on the host/target platform? If so, using |
How about moving the docs to |
@alexcrichton I take it you mean put the documentation source in |
…, r=flip1995 Improve error messages format Following review in rust-lang/rust-clippy#11845, since there is already suggestions, no need to add the second part of the sentence every time. r? `@flip1995` changelog: Improve some error messages
Putting our doc artifacts in the same directory as the source causes problems like in #11833, and it makes some problems for
make clean
when we do an in-tree build (I think we probably don't clean some of the docs because of this). Let's do the build into a different directory, maybedoc-build
, ordoc/build
? Any better ideas?The text was updated successfully, but these errors were encountered: