Skip to content

Conversation

@Teufelchen1
Copy link
Contributor

@Teufelchen1 Teufelchen1 commented Dec 8, 2025

Contribution description

This is a continuation of #20447.

The first commit is basically a rebase of that PR onto the current master (missing a lot var-name changes that are not relevant to the second commit).
The second commit is a first idea on how to solve the problem that cpus are features and therefore have to be in the features_existing.inc.mk. The solution taken here is to have a second features_existing.inc.mk in the external CPU dir.

Note that this PR does not necessarily replace the original one. I just need a place to test and discuss the options for this specific issue.

Testing procedure

TBD

Issues/PRs references

#20447

@github-actions github-actions bot added the Area: build system Area: Build system label Dec 8, 2025

# Detect provided / used / optional features that do not exist
include $(RIOTMAKE)/features_existing.inc.mk
-include $(EXTERNAL_CPU_DIRS)/features_existing.inc.mk
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs to be converted to an iterator, should this approach be chosen.

@AnnsAnns
Copy link
Member

AnnsAnns commented Dec 9, 2025

I think this approach is quite alright, esp. considering that, while useful, this will only impact the very very few external cpus that (should ever) exist. Would be neat to have a test for this approach though just to make sure that we don't break it by accident, ty for this 👍

@crasbe crasbe added Type: new feature The issue requests / The PR implemements a new feature for RIOT Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR labels Dec 9, 2025
@Teufelchen1 Teufelchen1 marked this pull request as draft December 11, 2025 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: build system Area: Build system Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR Type: new feature The issue requests / The PR implemements a new feature for RIOT

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants