Add infrastructure to toolchain.cmake to allow repositories to use a custom C++ standard library implementation#14728
Merged
jkoritzinsky merged 1 commit intodotnet:mainfrom Apr 20, 2024
Conversation
…custom C++ standard library implementation
jkotas
approved these changes
Apr 20, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As part of the discussion in dotnet/runtime#101088 and offline, we're strongly considering using a less "default" (but still supported) setup for our C++ standard library dependencies in dotnet/runtime to ensure we are using as little code from the Ubuntu 16.04 rootfs in our products as possible.
This PR provides the infrastructure for dotnet/runtime to reference a custom standard library that we insert into the rootfs as part of our docker image production.