RTEMS | Add support for tool build key (#5521)

[Chris Johns (@chris)]

Chris Johns created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5521



## Summary

A build key has been added to the RTEMS tools built by the RSB. The issue https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/130 tracks the changes. We need to add support to this repo to check for a suitable key before proceeding with configuration or building.

The build key is a date in reserve dot notation of `yyyy.mm.dd`. The check is performed on each architecture gcc tool used in a build. If the checker cannot locate a valid build key label the check passes. We can assume any tool without a build key is the users responsibility to make sure it is OK to use. 

A check is:

1. Get the gcc version string for an architecture
2. Locate the `Build:` key in the `()` section of the version string
3. Validate the build key value has the format of `dddd.dd.dd` where `d` is `0` to `9`
4. Check each part of the dot notation against the build system value
5. If the gcc build key is greater than or after the build system key the tools are suitable

The `rtems.git` build key defines the build key it supports. A later tool set may be provides `rtems.git` is compatible with. The build system build key is only updated when there is a specific requirement for a build of tools.

The implementation can be using `spec` files and the build key in a `spec` file or it can be coded into `wscript` in Python.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5521
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260313/3567ec32/attachment.htm>