README: one include() line adds this module to your own build - #19
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The build section now leads with the MicroPython 1.29 path: clone the repo anywhere and add include("/path/to/audioif/manifest.py") to the manifest your build already uses. Then the pre-1.29 USER_C_MODULES fallback, and one sentence on the FROZEN_MANIFEST trap (a new manifest must include the port's default or asyncio and friends go missing). Stale v1.28 / workspace references in that section are gone.
Build-proven: unix port, MicroPython v1.29.0, standard variant manifest plus audiodsp's and this repo's include(); audiobusio and _audioif import and audiopump.driver() answers 'pthread'. The esp32 path was checked by reading micropython.cmake.