RTEMS | waf: Invalidate build on configuration change (!1093)

Wed Mar 4 22:08:07 UTC 2026

SHIVAM DEOLANKAR commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1093#note_144266

Thank you for the suggestion. I inspected the link step for the affected BSPs (e.g. aarch64/zynqmp_apu) and the link command does not appear to use an explicit linker script (no -T flag). The executable is produced by linking the RTEMS libraries (lrtemscpu, lrtemsbsp, etc.).

![image.png](/uploads/8945331f6ed788d9162cec4c8fd94f6d/image.png){width=838 height=304}

Based on this, the issue does not seem to be caused by missing linker script dependencies. Instead it appears that configuration state (such as RTEMS_SMP) is not reflected in the task signature. Since configuration changes do not modify compiler flags or source inputs, Waf considers previously compiled objects valid and reuses them.

The configuration fingerprint approach ensures that configuration changes affect the compiler flags, which correctly invalidates existing objects and triggers a rebuild.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1093#note_144266
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/20260304/a2ddb3e4/attachment.htm>