-
Notifications
You must be signed in to change notification settings - Fork 13
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
check for std symbols #2
Comments
I explored that route, but ultimately got stuck on isolating the binary part out of the I'm generally pro doing that, though most likely as an optional thing if it requires |
@gnzlbg I tried out Apart from the Not the most beautiful solution, but probably the best we can do for post-compilation checks right now. |
Sounds good, that's what I ended up doing more or less. One might need to try using the |
Good news! At a recent meetup someone told me that I I'm currently working on adding that as a new mode to |
Test whether the final rlib or binary contain any
std
symbols or not.The
llvm-tools-preview
component contains anllvm-nm
that can be used to list all symbols in a binary, and thecargo-binutils
sub-command can be used to find the appropriatellvm-nm
binary for the current toolchain (https://internals.rust-lang.org/t/llvm-tools-a-new-rustup-component-for-binary-inspection-objdump-nm-size-and-profiling-profdata/7830/9).With that one can check whether the final binary contains any
std
library symbols, a check that must pass independently of what all other checks say.The text was updated successfully, but these errors were encountered: