Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Windows arm-zephyr-eabi GDB requires Python 3.8 #512

Closed
skalldri opened this issue Jul 4, 2022 · 1 comment
Closed

Windows arm-zephyr-eabi GDB requires Python 3.8 #512

skalldri opened this issue Jul 4, 2022 · 1 comment
Labels

Comments

@skalldri
Copy link

skalldri commented Jul 4, 2022

Hi there,

The currently released Zephyr SDK for Windows (0.14.2) requires Python 3.8 be installed for certain components to work. So far, I've found that the arm-zephyr-eabi GDB instance needs access to python38.dll to function.

The most recent version of Zephyr asks users to install Python 3.10 (or perhaps more accurately, Python 3.10 is what ships with Chocolatey by default on Windows currently). Python 3.10 isn't compatible with the released Zephyr SDK, it needs Python 3.8. This means that users need to install two versions of Python side-by-side to use Zephyr and it's SDK.

Could this potentially be fixed, so that Zephyr and the SDK use the same version of Python? Or could the SDK ship with a re-distributable Python installer to avoid this issue?

@stephanosio
Copy link
Member

Please see #407 (comment).

If you actually require the Python scripting capability, you can install the Python 3.8 by running the following command (there is a PR to add this to the Getting Started Guide):

choco install python --version=3.8.0

Also from the upcoming Zephyr SDK release (0.15.0), the default GDB executable (*-gdb) will be built without the Python scripting support and no longer require libpython; instead, a separate Python scripting capable GDB variant (*-gdb-py) will be provided in case you actually need this feature.

@zephyrproject-rtos zephyrproject-rtos locked and limited conversation to collaborators Jul 5, 2022
@stephanosio stephanosio converted this issue into discussion #514 Jul 5, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Projects
None yet
Development

No branches or pull requests

2 participants