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

Fix build #81

Closed
wnienhaus opened this issue Aug 19, 2022 · 0 comments · Fixed by #82
Closed

Fix build #81

wnienhaus opened this issue Aug 19, 2022 · 0 comments · Fixed by #82

Comments

@wnienhaus
Copy link
Collaborator

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.

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.

Fixes micropython#81
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

Successfully merging a pull request may close this issue.

1 participant