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

Chris Johns (@chris) gitlab at rtems.org
Sun Jul 7 22:19:41 UTC 2024




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


This looks close to what is need. I am sure you will discover further detail that will need resolving. Some points aret:

1. Where is the location of `stdcxx.py` in the RSB?
2. The label `gcc_version` is being used so another macro name is needed
3. To execute a shell command in a config file wrap it in `%()`. The output to `stdout` is returned and assigned to the macro
4. You will need to locate the staged gcc executable. It will be under [%{build_dir}/$SB_BIULD_ROOT](https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/blob/main/source-builder/config/gcc-common-1.cfg?ref_type=heads#L220)<span dir=""> </span>path after being installed
5. I always `cat a_file | sed -e 's/xxx/yyy/g' > ${build_dir}/$SB_BUILD_ROOT/share/gdb/what-ever/stdcxx.py` which using `sed` to filter a file
6. The `%{name}` macros are expanded when the config is processed by the RSB. The shell variables are only valid when the build is running in the shell

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/issues/5#note_108827
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/20240707/eb2c6054/attachment.htm>


More information about the bugs mailing list