When using lv_micropython based firmware, REPL reports an old version of Micropython while the code is up to date.
Reason for this is the command ‘git describe’, which is used by the script makeversionhdr.py.
‘git describe’ itsself echos the newest tag avaliable, which is in this case an old one.
I watched some videos about git online and it may be I found a clue to the ‘git describe’-effect in the
lv_micropython repo, which reports the wrong version of micropython.
This may be the result of using ‘git add submodule’ in a repo, which then “fixed” and get no more updates even when doing a git pull in the parent repo.
One needs to do a git checkout of a specific version of that submodule to get an update and getting all metadata updated as far as I understood the underlying mechanics.
I will try to follow that path (I git submodule added lv_bindings_micropython into my local micropython repo) – I am waiting for updates of the according repos online to check that.
Would it be possible that this mechanics may also apply to the lv_micropython repo online?