tools/makemanifest.py: Add support for optional board-level manifest. #7624
Conversation
* Allow adding board-level frozen modules via optional board-manifest.
* Example usage: include("$(BOARD_DIR)/manifest.py", optional=True)
67a1c4d to
b3f150f
Compare
The idea with making manifest a Python file is that you can do things like this: import os
if os.path.isfile(...):
include(...) |
|
But it's not possible to resolve variables like |
Correct. In that case it would make sense to expose |
|
The way this was currently intended to work was that the board-level manifest would be the entry point, and then would include the port-level manifest. i.e. boards/FOO_BOARD/mpconfigboard.mk would set Or am I misunderstanding the use case? I can see that it would be nice for a board-level manifest to be automatically found by the port-level one, but in some cases you actually want the board-level one to bypass the port-level one. The example here does exactly that https://github.com/micropython/micropython-example-boards/tree/main/boards/CUSTOM_PYBV11 |
Yes that's the use case, and I see your point and agree. I was actually looking at the RP2 port which doesn't allow overriding the manifest variable, so I'll close this PR and I sent this fix instead: #7628 |
Is there another way to do this already that I've missed ?