Amar Takhar created an issue: https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/issues/9
## Summary <!--Please provide as much information as possible such as error messages or attaching logs--> The two changes in these MRs have been rejected and I need a solution from the RTEMS Builder GUI which I will lay out in this issue under the restrictions of how the GUI is made. Adding this here to record the history of the problem and why the changes were rejected. I have some of my own solutions but they are a lot of work that I wish to avoid as the GUI itself is a huge amount on its own. * https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/26 * https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/27 ## GUI restrictions The GUI itself holds no information about RTEMS or otherwise it is only designed to run the vertical stack / RTEMS tools. The GUI itself shares the commands it runs so users can then copy those commands to the commandline and run them on its own. This is by design, for example: {width=427 height=43} This lets the user copy and paste the command if they wish into a commandline and replicate what the GUI does. This restricts the GUI to running commands that are only available via the RSB or deployment. Building RTEMS only comes from deployment. The purpose is to: * Clone the CLI experience for the user * Not for additions to be in the RTEMS tool stack and _not_ the GUI The GUI is not part of the vertical stack, while it sits on top of it all it can do is use other tools but not do anything itself any new features must be added somewhere in or underneath RTEMS deployment. * The GUI _can_ use the RSB to populate itself but it can't run commands in the RSB to _build_ RTEMS it can only use rtems-deployment. ## RTEMS BSP data In order to populate the GUI with a list of available BSPs it needs a list of architectures and BSPs in order to feed to rtems-deployment for building. Whatever restrictions that come from versions must be available to the rtems-deployment CLI. The GUI only runs commands and cannot internally restrict anything outside of what the vertical stack already offers. ## What the GUI cannot do * It can't run commands outside of the RSB or rtems-deployment * It can't hold data outside of the RSB or rtems-deployment * It can't be part of the vertical stack ## What the GUI can do * It can run commands in the RSB or rtems-deployment to populate itself which would also serve as a way for users to get a list of available items to build. * It can run commands in rtems-deployment to build RTEMS and a toolchain ## Conclusion With the above in mind there needs to be a way to solve what the original two MRs did. the JSON was a temp solution to get the GUI to a point where something better could be put in place. Since that has been rejected then I need a new way to do it keeping all of this in mind. -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/issues/9 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
