RTEMS Tools | Provide an RTEMS STD C++ script in Python (#5)

[Chris Johns (@chris)]

Chris Johns commented on a discussion: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/issues/5#note_108895


1. The support for gdb pretty printing is RTEMS specific so I think that should be under the `rtems/config` tree. The `gcc-common-1.cfg` is in the common area so I think the support eventually end up in the RTEMS side of things. I think we will have to progress to this point
2. Would it end up being confusing? How would know which value the variable holds? Remember the gcc version internal to gcc may not match the version in the macro `gcc_version`. For example we could have a git hash build of the gcc 13 branch. This work needs to know the internal value to find the path gcc will look.
3. The path `${build_top}` is not in the RSB source tree and you cannot assume the `build` is always in the RSB source. The `rtems-deployment` repo is example of extending the RSB configs. I think we need to find a way to get the path. I suggest using `--trace` and `--dry-run` and then reviewing the log and macro variables that are printed to see what is suitable

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/issues/5#note_108895
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/20240709/4ddb9f87/attachment.htm>