Move support to v2.7.x and v3.1.0

[pablogs9]

Signed-off-by: Pablo Garrido pablogs9@gmail.com

[uLipe]

@pablogs9 as I said here, to get this working we would need to update some points:

• USB-Serial now used device tree to get enabled, but applying this update will break the compatibillity with previous Zephyr releases;
• Wait ros2 accept the rcuitls patch, for the posix timer implementation and update the commit used by libmicroros, currently I created a diff and patching locally and wrote this instruction in the app I'm working on top of this module.

Also I'm taking some time to refactor the zephyr transports for serial to use the up to date DT macros instead of using device labels, this is compatible across zephyr releases and scalable as long Zephyr evolves, probably will push this PR today or tomorrow.

[uLipe]

Sure, I will take some time to look into :)

[pablogs9]

@mergify backport humble galactic foxy

[mergify]

backport humble galactic foxy

✅ Backports have been created

• #66 Move support to v2.7.x and v3.1.0 (backport #64) has been created for branch humble
• #67 Move support to v2.7.x and v3.1.0 (backport #64) has been created for branch galactic
• #68 Move support to v2.7.x and v3.1.0 (backport #64) has been created for branch foxy

[Acuadros95]

FYI @pablogs9 @uLipe , we need to change zephyr include paths for v.3.1.0 and beyond:

https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v3.1.0:

All Zephyr public headers have been moved to include/zephyr, meaning they
need to be prefixed with <zephyr/...> when included. Because this change
can potentially break many applications or libraries,
:kconfig:option:CONFIG_LEGACY_INCLUDE_PATH is provided to allow using the
old include path. This option is now enabled by default to allow a smooth
transition. In order to facilitate the migration to the new include prefix, a
script to automate the process is also provided:
:zephyr_file:scripts/utils/migrate_includes.py.

[uLipe]

Yes, altough this could be done in other PR, the kconfig option for legacy includes is only disabled to run apps under twister which is used to do unit tests for zephyr components. Le mer. 17 août 2022 à 07:45, Antonio Cuadros ***@***.***> a écrit :

…

FYI @pablogs9 <https://github.com/pablogs9> @uLipe <https://github.com/uLipe> , we need to change zephyr include paths for v.3.1.0 and beyond: https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v3.1.0: All Zephyr public headers have been moved to include/zephyr, meaning they need to be prefixed with <zephyr/...> when included. Because this change can potentially break many applications or libraries, :kconfig:option:CONFIG_LEGACY_INCLUDE_PATH is provided to allow using the old include path. This option is now enabled by default to allow a smooth transition. In order to facilitate the migration to the new include prefix, a script to automate the process is also provided: :zephyr_file:scripts/utils/migrate_includes.py. — Reply to this email directly, view it on GitHub <#64 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNWX5OPS7P4U4F7AZ33M3LVZS7D5ANCNFSM54367PPA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[pablogs9]

Do we have any define in the Zephyr build system indicating the version so we can conditionally include the correct header?