Sebastian Huber commented on a discussion on spec/build/cpukit/cpuriscv.yml: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1222#note_149262

 >    - cpukit/score/cpu/riscv/include/rtems/score/cpu.h
 >    - cpukit/score/cpu/riscv/include/rtems/score/cpu_asm.h
 >    - cpukit/score/cpu/riscv/include/rtems/score/cpuimpl.h
 > +  - contrib/cpukit/riscv-opcodes/encoding.h

I would have maintained the contributed sources through specialized build 
specification items: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/398#note_119194

With this approach all the file movements would have been unnecessary and we 
would not have an inflation of include paths. The conversion from Automake to 
waf did consolidate the include paths, now the development is reversed.

With a proper import/export specification, it would be easy to synchronize the 
contributed sources with the upstream with the help of tooling provided by 
[specmake](https://github.com/specthings/specmake).

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1222#note_149262
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

Reply via email to