-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
#27901 breaks mikroe_* shields overlay #29074
Comments
seems we need to define a rule on processing order, but let's first decide what the correct / expected behavior should be seen from the user perspective. And then from there determine the processing order in the build system. When looking at: then I would actually expect that what is specified in With this logic, the patch in: #27901 must be reverted, as change processing order seems to result in the definitions in the shield is taking precedence over the board. @mbolivar-nordic wouldn't you agree ? |
I don't use shields, so I think this is an @erwango question. |
Fixes: zephyrproject-rtos#29074 This reverts commit fc8f639. The suggestion provided in zephyrproject-rtos#27901 is impacting processing order of overlay files in a non-logical way, see zephyrproject-rtos#29074 discussion for details. Signed-off-by: Torsten Rasmussen <[email protected]>
Created: #29825 as followup to minimize the risk that this happens again. |
Fixes: #29074 This reverts commit fc8f639. The suggestion provided in #27901 is impacting processing order of overlay files in a non-logical way, see #29074 discussion for details. Signed-off-by: Torsten Rasmussen <[email protected]>
The change in order #27901 will put the cart before the horse when building with overlays.
To Reproduce
Expected behavior
Should build.
Impact
Does not build.
Excerpt from temporary dts file (lpcxpresso55s69_cpu0.dts.pre.tmp):
Possible resolution
Change the overlay include order or change the board overlay
The text was updated successfully, but these errors were encountered: