-
Notifications
You must be signed in to change notification settings - Fork 2.1k
cpu/stm32: simplify handling of generated IRQ header #21964
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
base: master
Are you sure you want to change the base?
Conversation
Output of |
|
IIRC, once this is in master, users who already built firmwares for stm32 will have to manually remove the previously generated STM32 IRQ headers. |
d77faa4 to
1f1b55a
Compare
- rename `irqs/<CPU_FAM>/irqs.h` to `irqs/<CPU_FAM>/stm32_irqs.h` to
reduce chance of a name conflict (`irqs.h` might not be unique)
- add `irqs/<CPU_FAM>` to the include paths
- add the `#include "stm32{f0,f1,f2,f3,f4,f7,l0,...}xx.h"` to the
generated `stm32_irqs.h`
==> Now we can just go for `#include "stm32_irqs.h` and drop a lot of
preprocessor conditionals
1f1b55a to
b60df58
Compare
|
I added a simple cleanup and a note to remove the cleanup after the next release branch has been created. This will only remove the |
|
Hmm, I wonder if it is better to just document that users should run |

Contribution description
irqs/<CPU_FAM>/irqs.htoirqs/<CPU_FAM>/stm32_irqs.hto reduce chance of a name conflict (irqs.hmight not be unique)irqs/<CPU_FAM>to the include paths#include "stm32{f0,f1,f2,f3,f4,f7,l0,...}xx.h"to the generatedstm32_irqs.h==> Now we can just go for
#include "stm32_irqs.hand drop a lot of preprocessor conditionalsTesting procedure
The generated binaries should not change
Issues/PRs references
None