Skip to content
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

Use of mp_obj_type_t Incompatible with latest micropython? #258

Closed
nord0296 opened this issue Feb 10, 2023 · 1 comment
Closed

Use of mp_obj_type_t Incompatible with latest micropython? #258

nord0296 opened this issue Feb 10, 2023 · 1 comment

Comments

@nord0296
Copy link

I have the lv_micropython building and running on a Pico W with Waveshare 2.8" ResTouch and realized the Pico W board was not in the lv_micropython fork as it was too old (I built for just Pico).

Rather than pulling in the board details to the lv_micropython fork, I tried to add the lv_binding_micropython submodule to a new clone of the latest micropython main repo.

I don't believe I have made any significant mistakes yet, but in trying to get it to build I'm seeing numerous errors that seem to imply the lv_bindings lib is not compatible with their allocation for mp_obj_type anymore.

The build errors helpfully (?) point to the wiki - https://github.com/micropython/micropython/wiki/Build-Troubleshooting and chasing it a little make it look like the code generated by gen_mpy.py is unaware of this change and using prior syntax (prior to micropython/micropython#8813)

Please let me know if I am mistaken in my analysis. Maybe if I want build a fairly up to date PicoW build I need to take another approach?

@amirgon
Copy link
Collaborator

amirgon commented Feb 10, 2023

lv_micropython is aligned to latest Micropython release, which is 1.19, not to Micropython head on git.
We are aware that Micropython recently changed some APIs and is not backward compatible.
When a new Micropython version is released, we will fix lv_micropython accordingly.

Until then, you can try using #242 which contains at least some of the fixes needed.

@amirgon amirgon closed this as completed Feb 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants