[SERVER-50587] Investigate the use of NINJA_SKIP Created: 27/Aug/20  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: Daniel Moody 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:
Related
related to SERVER-82537 Complete TODO listed in SERVER-50587 Needs Scheduling
Assigned Teams:
Server Development Platform
Participants:

 Description   

NINJA_SKIP will remove parity between SCons and Ninja build by causing Ninja to completely ignore a build node.

 

This can cause dependency issues if a given node built by Ninja is dependent on a NINJA_SKIP node, ninja would not know to rebuild if the NINJA_SKIP node changed.

 

NINJA_SKIP should at least put the node in the ninja TEMPLATES section with implicity dependencys so ninja can know when to reinvoke scons to build said node.


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