Uh oh!
There was an error while loading. Please reload this page.
Enable StripSymbols by default - #85139
Conversation
See discussion in dotnet/sdk#31739 (comment). Once this merges, we should: - [ ] Update the `dotnet new console -aot` template - [ ] Update the `dotnet new api -aot` template - [ ] Update docs and declare different defaults.
ghost
commented
Apr 21, 2023
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue DetailsSee discussion in dotnet/sdk#31739 (comment). Once this merges, we should:
Cc @dotnet/ilc-contrib @am11@DamianEdwards@eerhardt
|
Added When you commit this breaking change:
Tagging @dotnet/compat for awareness of the breaking change. |
MichalStrehovsky
commented
Apr 22, 2023
Cc @kotlarmilos@akoeplinger looks like there's an issue with the GenerateUnmanagedEntrypoints test when stripsymbols is specified. A wild guess is that this strips the symbols we actually need. Don't have a mac around to investigate. I'm going to enable StripSymbols on the test on mac so that we don't block this since GenerateUnmanagedEntrypoints is not an end user scenario. |
MichalStrehovsky
commented
Apr 22, 2023
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ivanpovazan
commented
Apr 24, 2023
I can look into this, as I added the test case. |
kotlarmilos
commented
Apr 24, 2023
@ivanpovazan Thanks! Let me know if the failure is caused by particular stripping options introduced in #81361. |
See discussion in dotnet/sdk#31739 (comment).
Once this merges, we should:
dotnet new console -aottemplatedotnet new api -aottemplateCc @dotnet/ilc-contrib @am11@DamianEdwards@eerhardt