Skip to content

install all used targets into the container when provisioning #242

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

Merged
merged 1 commit into from
Oct 26, 2018

Conversation

QuietMisdreavus
Copy link
Member

When i opened https://github.com/onur/docs.rs/pull/224, i had a problem where it couldn't generate docs for all the usual targets. I poked around again, and after adding some debug printing, it turns out that the Cargo invocation fails because it can't find the std to link the crate against - i.e. the target hadn't been installed in rustup. After adding the target(s) to the container, they all built just fine. This PR adds the installation of the required targets into the Vagrantfile, so that when someone provisions their environment, they get all the required targets right away.

@QuietMisdreavus
Copy link
Member Author

Based on a conversation with @onur today, i've updated this PR to only add targets for 64-bit macOS and Windows. Adding all 8 targets starts to run into space issues when running in the vagrant container.

@onur
Copy link
Member

onur commented Oct 26, 2018

I think this targets are enough for development. Adding all targets may slow us down.

@onur onur merged commit 903ae1f into rust-lang:master Oct 26, 2018
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

Successfully merging this pull request may close these issues.

2 participants