Skip to content

zephyr: Update generated file include path #17554

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dsch
Copy link

@dsch dsch commented Jun 23, 2025

Support disabled LEGACY_GENERATED_INCLUDE_PATH compatibility option.

Summary

Since Zephyr 3.7 generated include files are namespaced. That means all generated header files are located under zephyr/*. Currently the CONFIG_LEGACY_GENERATED_INCLUDE_PATH is enabled by default to support the old way of including generated header files. This change ensures the MicroPython port for Zephyr is ready for a future deprecation of the option.

See also:

@dsch dsch force-pushed the legacy-generated-include-path branch 4 times, most recently from e2d7241 to 5109824 Compare June 23, 2025 13:42
Support disabled LEGACY_GENERATED_INCLUDE_PATH compatibility option.
Since Zephyr 3.7 generated include files are namespaced.

See also: zephyrproject-rtos/zephyr@bbe5e1e6ebf4a1a66c0

Signed-off-by: David Schneider <schneidav81@gmail.com>
@dsch dsch force-pushed the legacy-generated-include-path branch from 5109824 to 061bc5c Compare June 24, 2025 13:17
Copy link
Member

@dpgeorge dpgeorge left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution. This looks good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants