-
Notifications
You must be signed in to change notification settings - Fork 113
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
Cannot open /mwldarm.response.template #339
Comments
this is an extremely vague error. are you able to open/edit it with a text editor? what directory did you put it in? |
@red031000 Yes I could open/edit whatever. I put it in the root directory of the project, and tried to change the directory via modifying common.mk file. It's not the directory problem for sure as I mentioned. I just gave up running on Windows itself, instead I turned to WSL Ubuntu with the exact same settings and succeeded compiling. There was no support for wine32 in recent version of Ubuntu, so before compiling I had to run this command
I hope this solution may help for some people just like me |
Checking in to see if this is resolved. The source of the error is that the current working directory was not determined correctly. There's a few hacks to support Linux platforms using WINE while still supporting WSL1, but it relies on parsing the shell's self-identification, and support is incomplete on our end. For now we recommend that Windows users use WSL as that is currently the most stable environment (followed by Linux and older Macs). For best performance, we recommend Intel CPUs, as project-level support for ARM hosts is incomplete. |
This issue has had no activity for 60 days and will be marked stale. If there is no further activity, it will be closed in 30 days. |
Win11, Samsung Galaxy Book2 pro 360
I ran make command on cygwin64 terminal on administrator permission.
I can confirm that another error occurs when the file mwldarm.response.template is not on the proper dir, so I'm wodering if it's about the user permission, but the result is same even I run it with runas.
I extracted the template file from nitroSDK from the contributor's discord, so nothing should be wrong.
The text was updated successfully, but these errors were encountered: