-
Notifications
You must be signed in to change notification settings - Fork 2k
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
cpu/stm32f1: Add Kconfig dependency modeling #16483
Conversation
Thus far it is only tested on |
61587cc
to
55a4817
Compare
Just testing with the CI to see what happens. |
there we go... Should be ready. |
fcd21cc
to
1f07edb
Compare
1f07edb
to
b91c631
Compare
|
There is no clear reason why this should be configurable and causes an abstraction of USEMODULE. The true reason is to make Kconfig easier but it seems having a variable in USEMODULE is a bit strange.
Also add better error message when kconfig or make includes a .cpp without cpp module.
32ec937
to
214b195
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI is happy and changes make sense. Let's go ahead with this one. ACK!
Many thanks, one small step for stm32f1 series, one leap for Kconfig. |
Contribution description
This adds the Kconfig dependency modeling to the stm32 cpu. This applies to all stm32 based boards but will only be checked for a stm32f1 series board to limit the size of the PR. Other series will be added in follow-up PRs with the required fixes.
nucleo-f103rb
withTEST_KCONFIG=1
Testing procedure
Murdock should test the binaries are matching the make build
Issues/PRs references
Based on #16487