We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Follow-up to #2152
The text was updated successfully, but these errors were encountered:
I prepared already medek/nasm-rs#28
Sorry, something went wrong.
Seems to be no response from the maintainer there. I hate to say we might want to fork it... but should we fork it?
We've forked it before. I guess we can fork it again.
Or we can write the check in build.rs directly. Once I'm fully awake I can send a pr if nobody beats me at it.
#2223
Successfully merging a pull request may close this issue.
Follow-up to #2152
The text was updated successfully, but these errors were encountered: