[SERVER-44985] Ninja builder should be able to correctly determine out of date-ness Created: 06/Dec/19  Updated: 06/Dec/22  Resolved: 28/Jan/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mathew Robinson (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-45302 Only write Ninja file if the contents... Closed
Assigned Teams:
Server Development Platform
Operating System: ALL
Sprint: Dev Platform 2020-02-24
Participants:

 Description   

After generating a fresh ninja file and executing ninja it will immediately regenerate itself. This is because Ninja does not know anything about the SCons* files on first run so assumes they are out of date and re-runs the generation command.

We should either populate .ninja_deps so it's aware it's been recently generated or teach the SCons Ninja builder how to determine it's out of date-ness so when ninja runs the generation command it will only determine there's no work to do.


Generated at Thu Feb 08 05:07:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.