[SERVER-64825] Debugger mongo pretty printer support files should reflect selected toolchain and be staged to install Created: 23/Mar/22  Updated: 28/Aug/23  Resolved: 28/Aug/23

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

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:
Related
related to SERVER-62995 Update pretty printers as needed to w... Closed
Assigned Teams:
Server Development Platform
Participants:

 Description   

The mongo pretty printer support files currently hardcode assumptions about what toolchain and standard library were used, but these assumptions do not always hold true. Instead of hardcoding this information, we should let the build system propagate its knowledge of the toolchain and runtime and associated paths into these files, treating the source tree versions as templates, and staging the substituted versions into the installation directory. This will ensure that any given mongodb installation has pretty printer support that correctly reflects the toolchain and runtime library choices. It has the additional benefit of making it possible to use the pretty printers with only an installation of the product, while we currently require a clone of the sources.


Generated at Thu Feb 08 06:01:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.