RTEMS Deployment | config: Add support for generic builds (!26)

[Amar Takhar (@amar)]

Amar Takhar created a merge request: https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/26

Project:Branches: amar/rtems-deployment:generic to rtems/tools/rtems-deployment:main
Author:   Amar Takhar
Assignee: Amar Takhar
Reviewer: Chris Johns


## Summary

A note about this implementation: there is duplication of code for now because I was unsure of exactly what extra support we'd need in the future. Since these are not files that exist on disk there was no easy way to add this kind of support outside of 'tar'. This is the only type of dynamic builds we should have so it makes sense that it needs to be out-of-band and it will eventually change even more when we add options like adding / removing libbsd, networking or even micropython in the future.

This works the same as deployment itself use `waf list` to see targets then select one of the `generic/*` targets to build.

The generic builds are pseudo builds that use the files in generic/\* including bsp.json which is generated by rtems-bsps

This generates configs on-demand using the files in generic/ to build a generic BSP config.

This is not customisable that's not the point if someone wishes to do so they can copy the files out of out/ and put them in config/

The reason these are dynamically generated rather than statically on-disk is to allow bsp.json to change as it needs. Eventually I want to add options each BSP supports so they can be added on the deployment commandline and eventually in the GUI.

<!--Default settings, if it is a dropdown it will set after submission-->

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/26
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/20250728/742253c2/attachment.htm>