RTEMS Source Builder | Draft: RSB modifications to install stdcxx.py in gdb/python/rtems (!35)

[Suraj Kumar (@the.m3chanic)]

Suraj  Kumar commented on a discussion on source-builder/config/gcc-common-1.cfg: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/35#note_110079

 > +  # be cut with ':' because _configdir contains 4 copies of 
 > +  # the same path
 > +  %define rtems_configdir %(echo %{_configdir} | cut -d':' -f1)
 > +
 > +  # Path to the location of the template script. 
 > +  %define stdcxx_template %{rtems_configdir}/stdcxx-template.py
 > +
 > +  # Get the current GCC version of the target being built. 
 > +  %define rsb_rtems_gcc_version %(%{_bindir}/%{_target}-gcc --version | head -1 | awk '{print $3}')
 > +
 > +  # Path to the target location of the script: gdb/python 
 > +  %define stdcxx_script %{_prefix}/share/gdb/python/rtems/stdcxx.py
 > +
 > +  # Modify the template script and update the current GCC version 
 > +  # and place it in the target location. 
 > +  cat %{stdcxx_template} | sed "s/@RSB_GCC_VERSION@/%{rsb_rtems_gcc_version}/g" > %{stdcxx_script}

Yeah sure, that would work too. I assume that including files will have the variables/macros from the file including it too (?) so that would make for a more modular approach. 

I think we can have a file, say `rtems-gcc-preinstall.cfg`, under `rtems/config/tools`, which can have the same changes as my commit, and then have a check like so: 

```
%if %{_target} =~ ".*-rtems.*"
  %include %{_configdir}/rtems/tools/gcc-pre-install.cfg
%endif
```

How does that sound?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/35#note_110079
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/20240727/0a798b6b/attachment-0001.htm>