-
Notifications
You must be signed in to change notification settings - Fork 211
docs.rs should ignore .cargo/config #647
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
Hmm I thought we fixed this in #633 ... In the meantime you can workaround it by removing .cargo/config. Maybe the issue is that since we don't pass I wish there were a way to get cargo to tell us what target it plans to build ... |
The fact that it works locally but not in production is also very confusing, I have no idea what could cause that. |
Oh I do have an idea - if you'd set |
That makes sense! I removed every image and volume I had locally and reran the build which reproduces the error I see on docs.rs. I've changed the docs.rs config in [package.metadata.docs.rs]
targets = [ "thumbv7m-none-eabi", "thumbv7em-none-eabihf" ] The local build now passes on a fresh cache. Is that the best way to go? I realise it's a very recent addition but if it works on docs.rs then it works great for me 😁. |
Yes, that should work. Thanks for working with us, I'm glad the new feature is helpful! |
Fixing the root problem should be basically the same steps as #555 (comment), rustwide should remove |
Thanks for the suggestions! My builds are working again. Please close this issue if you think it should be :) |
I'll open a new issue for ignoring |
Crate name:
sh1106
Build failure link: https://docs.rs/crate/sh1106/0.3.0/builds/231814
Additional details:
I'm building a no_std crate targeting
thumbv7m-none-eabi
, etc. To get docs.rs builds working again, I added the following to myCargo.toml
:Which doesn't seem to have an effect, but only on docs.rs. If I build it locally using the
docs.rs
repo and the following command, it builds fine.docker-compose run -v "$(realpath ~/Repositories/sh1106)":/build web build crate --local /build
I do have a
.cargo/config
with the following at the end which may be causing issues?The text was updated successfully, but these errors were encountered: