Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-57393

Replace use of for_signature based generators with scanners

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • 6.0 Desired
    • None
    • None
    • None
    • Server Development Platform

    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 SERVER-55833, we learned of some of the downsides of this approach, and that we should instead be making proper use of Scanners to achieve this effect.

      Revisit our signature based injections and figure out how to use Scanners for those purposes instead.

      Attachments

        Activity

          People

            backlog-server-devplatform [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: