-
Notifications
You must be signed in to change notification settings - Fork 385
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
Allow specifying volumes in Cross.toml
.
#443
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
bors merge
Build succeeded: |
@@ -152,10 +170,10 @@ pub fn run(target: &Target, | |||
.args(&["-v", &format!("{}:/cargo:Z", cargo_dir.display())]) | |||
// Prevent `bin` from being mounted inside the Docker container. | |||
.args(&["-v", "/cargo/bin"]) | |||
.args(&["-v", &format!("{}:/project:Z", mount_root.display())]) | |||
.args(&["-v", &format!("{}:/{}:Z", mount_root.display(), mount_root.display())]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change will make it impossible to use a rustc wrapper with Cargo, which is the only way to pass custom flags due to #463, and the wrapper path needs to be absolute.
Setting it to /project/my-wrapper.sh
works just fine, but if the mount point is changed, there is no easy way to pass the absolute path to the wrapper.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, actually I already have to do something different for cross builds vs. native builds, so maybe this won't be that big of a deal? It's certainly a breaking change though.
No description provided.