Closed Tomiyou closed 11 months ago
I don't think you're doing anything wrong. The reason it doesn't error with the arm architecture is because we can only run strip
on native binaries for each platform, so strip is ignored when cross-compiling.
I just haven't tested this action with a crate with multiple binaries.
Can you give me a link to the action you ran for your repo? That'll help me figure out the exact fix. A PR would also be welcome.
This should be fixed in v0.0.10.
I have a Cargo.toml which specifies multiple binaries:
For some reason,
strip
command fails with errorNo such file
when building forx86_64_unknown_linux-musl
, but success without issue forarmv7-unknown-linux-musleabihf
:My
ci.yaml
file.I have tried to reproduce this issue locally using the command below, but everything goes well (binary exists as it should). Only when running the build via this repo's GitHub action do I encounter any issues.
Is this a bug or am I doing something wrong?