Skip to content
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

Documentation-only builds shouldn't fail because of missing dependencies #13

Closed
kornelski opened this issue Apr 21, 2018 · 2 comments
Closed

Comments

@kornelski
Copy link

https://github.com/onur/docs.rs/issues/147 (it's not exactly CI, but in the family of "the build fails on someone else's headless computer")

cargo doc runs a full build, and fails if any build.rs script fails. This is a problem for docs.rs, because it can't build documentation for -sys crates that usually require a specific library installed on the system (e.g. ffmpeg-sys won't build without a specific version of ffmpeg, so it doesn't get documented).

At very least there should be some cfg(doc) or env variable to detect docs build, so that tricky bits not relevant to the documentation can be skipped. Maybe Cargo/rustdoc could be instructed to plow through build failures and document as much as it can?

@epage
Copy link
Contributor

epage commented Apr 21, 2018

Let me see what can be turned into something tangible for crate-ci org to work on for this. Our focus is more on streamlining crate management through documentation, tooling, and advocating for fixing problems.

This sounds like a problem within existing tooling and you've opened a related issue with the respective tool. So is this more seeking to raise awareness for getting help advocating for your problem?

@kornelski
Copy link
Author

OK, that's probably out of scope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants