Only enable content signatures for SConscripts in ninja generation

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Development Platform
    • Dev Platform 2020-02-24
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the content signature system is not working for the ninja file itself. This causes an awkward bootstrapping step for new users where they have to generate a ninja file then run ninja which will immediately regenerate the ninja file.

      We should improve this by teaching SCons how to actually determine out of date-ness for the ninja files. This will also allow us to eventually move to incremental ninja generation.

            Assignee:
            [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
            Reporter:
            Mathew Robinson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: