-
Notifications
You must be signed in to change notification settings - Fork 166
Build documentation for *docs.rs* website #5
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
Is this to check that the docs can build? As far as I know, docs.rs automattically builds the documentation when updates are pushed to crates.io. However, docs.rs does seem to have failed to build the docs so far. All using |
Yes, I think the docs will not build on docs.rs because of Tectonic's dependencies on various native C libraries. I am not sure of the best way to deal with this. But this connects to the larger challenge of making Tectonic build more comfortably within the Cargo/Rust ecosystem (cf #15). |
Ah yes, you're right about that @musoke. Maybe docs.rs can somehow be told to ignore the native dependencies though, when generating docs? I can have a look into this at some point, perhaps. |
Didn't dig too deep, but here are some relevant links:
|
Yes, I believe 73 would fix the issue, and be the more elegant solution. |
I've just published version 0.1.6 of the crate, and confirm that we're now available on docs.rs! |
Reqwest client should be destroyed before forking to avoid threading issue. This is done by using thread local storage, that is initialized and used by geturl and cleared by texpresso. Alternative: use pthread_atfork in reqwest to properly handle fork.
Reqwest client should be destroyed before forking to avoid threading issue. This is done by using thread local storage, that is initialized and used by geturl and cleared by texpresso. Alternative: use pthread_atfork in reqwest to properly handle fork.
Let's make sure Travis does this automatically too.
The text was updated successfully, but these errors were encountered: