You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our last build just failed because MicroPython seems to have changed where the unix binary is output during build.
...log lines removed...
LINK build-standard/micropython
text data bss dec hex filename
554831 59016 2288 616135 966c7 build-standard/micropython
/home/runner/work/_temp/10e837c9-129d-409f-ac05-01ff729067c6.sh: line 12: micropython: command not found
The last few lines of the build log seem to show that the binary is now output to the build-standard subdirectory, while our build script runs micropyton from the current directory.
The text was updated successfully, but these errors were encountered:
wnienhaus
added a commit
to wnienhaus/micropython-esp32-ulp
that referenced
this issue
Aug 20, 2022
The MicroPython project changed their CI scripts slightly
which resulted in the unix port binary being output to a
subdirectory (build-standard) instead of the current
directory as before. This broke our build process.
This commit updates our build script to search for
the micropython binary in the correct subdirectory.
Fixesmicropython#81
Our last build just failed because MicroPython seems to have changed where the unix binary is output during build.
The last few lines of the build log seem to show that the binary is now output to the
build-standard
subdirectory, while our build script runsmicropyton
from the current directory.The text was updated successfully, but these errors were encountered: