Skip to content
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

boot: zephyr: Remove broken target config header feature #2069

Merged
merged 1 commit into from
Sep 27, 2024

Conversation

joerchan
Copy link
Contributor

Remove broken target config header feature.
This has been broken for more than 6 years, and seeing as nobody noticed it should be ok to remove it.

Broken because if(EXISTS path-to-file-or-directory) uses relative path. From cmake documentation:
"Behavior is well-defined only for explicit full paths".

Secondly ${BOARD}.h does not account for changes introduced in hwmv2 where BOARD_QUALIFIER maybe should be handled as well.

Also, who will put their board config files here?

Remove broken target config header feature.
This has been broken for more than 6 years, and seeing as nobody noticed
it should be ok to remove it.

Broken because if(EXISTS path-to-file-or-directory) uses relative path.
From cmake documentation:
"Behavior is well-defined only for explicit full paths".

Secondly ${BOARD}.h does not account for changes introduced in hwmv2
where BOARD_QUALIFIER maybe should be handled as well.

Also, who will put their board config files here?

Signed-off-by: Joakim Andersson <joerchan@gmail.com>
@nordicjm nordicjm added the area: zephyr Affects the Zephyr port label Sep 24, 2024
@nordicjm nordicjm merged commit f9fc591 into mcu-tools:main Sep 27, 2024
58 checks passed
@joerchan joerchan deleted the remove-target-config branch September 27, 2024 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: zephyr Affects the Zephyr port
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants