-
Notifications
You must be signed in to change notification settings - Fork 644
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
[CI binary release] create a workflow for binary release for Windows #1567
Comments
Be noticed:
|
Hi, how is this progressing? Edit: Is there something I can do to help? |
We don't have enough resource to start it . It will be very helpful if you are willing to take the task 😃 |
Nobody in their right mind would volontarily compile on Windows. Until Microsofts allows redistribution of the cl.exe compiler that is! Oh well, sad that WASM wont happen after all this work... |
why not use mingw? |
You want the compiler to be portable in a zip and I have that for cl.exe now after extracting it from VS. You might be able to use this in the same way but I haven't tried because I have my setup working: |
can anyone provide step by step instructions how can i do this? :) |
I think if they had that they would have compiled it already. |
Great to see that you finally made a iwasm.exe, but you probably should compile it to 32-bit too because around half of the projects on Windows are still running 32-bit since there is no reason to move to 64-bit there until Intel removes 32-bit from their CPUs and even then they will be properly emulated I'm sure. Also would be great with a way to use iwasm from your project and for that you need a .dll and a simple tutorial, sort of what was done here: |
WASM_ENABLE_
optionsThe text was updated successfully, but these errors were encountered: