-
Notifications
You must be signed in to change notification settings - Fork 61
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
Build without SIMD #121
Comments
You can recomplie |
What is |
I suppose they're installed with this? https://medium.com/wasmer/wasienv-wasi-development-workflow-for-humans-1811d9a50345 |
Is there a Discord channel or somewhere else I can go for questions during my build process? I've got things popping up and if I could just get ahold of someone that would make things much easier. |
|
I have successfully compiled and have wasmedge-quickjs working in our environment without SIMD. What do you think about making this a Cargo feature or somehow allowing wasmedge-quickjs to have this on be default by able to be turned off? |
How about downloading quickjs-wasi and building libquickjs.a every time during compilation? |
Sounds fine for my use case, we aren't often changing wasmedge-quickjs. |
Our environment does not support SIMD. I am not sure how to build wasmedge-quickjs without SIMD. I found this PR: #32 (comment)
I've tried removing the Rust compiler flag but we still get a SIMD validation error in our environment.
lib/libquickjs.a
seems to have been compiled with SIMD128 support. How do I recomplielib/libquickjs.a
to remove that?The text was updated successfully, but these errors were encountered: