-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
west signing seems to be broken on windows #31876
Comments
@thedjnK what exact commands did you run? Could you please document those here so that we can try to reproduce? |
@thedjnK I think what's going on here is that you neither have Without imgtool installed from python.org says that the default installer should make the right file associations: https://docs.python.org/3.9/using/windows.html#from-file-associations However, that's not working on my Windows setup, either. I'll think about how to fix this, but in the meantime, you have these workarounds:
|
@nashif consider changing to priority low based on the above diagnosis |
Done now. |
@mbolivar-nordic I've checked and python files are associated with python 3.7, if I create an empty .py file and run it, I get the python console open and close very quickly. I didn't have imgtool installed via pip as I assumed it would use the bundled version with zephyr as it used to do in zephyr 1.x, so I've installed imgtool via pip and I'm still getting the same result:
|
Did you try with a pristine build? I can no longer reproduce the error on my windows machine after installing imgtool. |
Exact commands were:
|
I'm building hello_world successfully with this command after running
The above comes from the west sign docs here: https://docs.zephyrproject.org/latest/guides/west/sign.html Can you try that, to see if perhaps it's a Kconfig issue? |
@mbolivar-nordic Ah yes, after clearing the build directory and re-generating it, it's now building and signing, thank you |
We can't trust that a python file is executable on Windows, regardless of what the mode bits say. When we find that imgtool is a .py file, run 'python imgtool.py' instead of 'imgtool.py' on that platform. Fixes: zephyrproject-rtos#31876 Signed-off-by: Martí Bolívar <[email protected]>
@mbolivar-nordic tested and that patch resolves the issue, thank you |
Thanks for testing! |
We can't trust that a python file is executable on Windows, regardless of what the mode bits say. When we find that imgtool is a .py file, run 'python imgtool.py' instead of 'imgtool.py' on that platform. Fixes: #31876 Signed-off-by: Martí Bolívar <[email protected]>
Describe the bug
Trying to build a signed image, after running ninja it fails at the signing step with an error that %1 is not a valid win32 application and no signed image is created
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The application to be signed
Impact
Showstopper
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: