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
I have several build profiles that need the same base C code, but define which idf components are included as well as what User C Modules are used based on the profile selected where profiles are specified by the board name.
One thing that could be added to this PR is the ability to include the main directories for the boards to a directory outside of the Micropython code tree so there is not a ton of board definitions in the main Micropython directory
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have several build profiles that need the same base C code, but define which idf components are included as well as what User C Modules are used based on the profile selected where profiles are specified by the board name.
I have edited esp32/CMakeFiles.txt and usermod.cmake to implement this feature.
See PR, https://github.com/micropython/micropython/pull/14127/files
To see what an implementation would look like, see the board profiles here
https://github.com/gentijo/micropython/tree/rmp_micropython_modules/ports/esp32
and the selection of User C Modules here
https://github.com/gentijo/ROSMicroPy/tree/reorg-modules/modules
One thing that could be added to this PR is the ability to include the main directories for the boards to a directory outside of the Micropython code tree so there is not a ton of board definitions in the main Micropython directory
Beta Was this translation helpful? Give feedback.
All reactions