Intended way of including python libraries (frozen) in the build... #9381
-
Hello, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Yes. The idea is that you can write your own Your custom manifest is free to use any of the base ones by The next step up is to define your own custom board definition (which sounds like might be useful to you if you're building a custom board) which lets you configure much more (via a custom mpconfigboard.cmake and mpconfigboard.h). These also can live in your own repo. See https://github.com/micropython/micropython-example-boards (This is a bit of an FAQ, and we really need to write more documentation on this process...). |
Beta Was this translation helpful? Give feedback.
Yes. The idea is that you can write your own
manifest.py
(which lives outside the main repo, in your own repo ideally) and then pass that to the build withmake BOARD=... FROZEN_MANIFEST=...path...
.Your custom manifest is free to use any of the base ones by
include()
-ing the port or board manifests.The next step up is to define your own custom board definition (which sounds like might be useful to you if you're building a custom board) which lets you configure much more (via a custom mpconfigboard.cmake and mpconfigboard.h). These also can live in your own repo. See https://github.com/micropython/micropython-example-boards
(This is a bit of an FAQ…