[SERVER-57393] Replace use of for_signature based generators with scanners Created: 03/Jun/21 Updated: 27/Oct/23 Resolved: 27/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0 Desired |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Server Development Platform
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
There are several places in the codebase where we use SCons generators with meaningful for_signature handling to ensure that changes to certain sorts of files (e.g. sanitizer suppression lists or symbol export lists) cause rebuilds. We are sort of cheating though, since what we are changing with those generators is the build signature of the target, and not properly introducing a real implicit dependency. While implementing support for forced includes in Revisit our signature based injections and figure out how to use Scanners for those purposes instead. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 17/Mar/22 ] |
|
We think a way to tackle this might be to build a generic target scanner that runs a list of sub-scanners as specified in an environment variable, which can then be overridden on a per-builder call. Building that tool might make building |