You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I enable binary stripping in a Cargo.toml release profile, then the cross build emits a warning about how it doesn't know how to strip symbols. Presumably because the binary is targeting a different operating system than the container guest operating system.
Perhaps we need the Docker images to install an additional tool for this?
The text was updated successfully, but these errors were encountered:
I seem to remember this one occurring for the aarch64-apple-darwin target. It's actually a warning rather than an error, so among lots of other output, I nearly missed it.
My love of cross is expressed in terms of porting my Rust projects to as many of the rustup targets as physically possible. So ideally I would like to see strip support working for all of the targets.
Perhaps stripping can be resolved by installing an additional package, or tweaking a config file somewhere. But maybe cargo and/or rustc would benefit from improving how they look for strip commands when cross compiling, not sure.
When I enable binary stripping in a Cargo.toml release profile, then the cross build emits a warning about how it doesn't know how to strip symbols. Presumably because the binary is targeting a different operating system than the container guest operating system.
Perhaps we need the Docker images to install an additional tool for this?
The text was updated successfully, but these errors were encountered: