-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wasm] Allow assemblies to be skipped for AOTMode=AotInterp #49446
Conversation
.. the targets/props .
.. to allow skipping AOT, per assembly.
This was added earlier to support blazor workload which only uses AOT. But that has since been fixed to correctly use `WasmBuildApp`+`@(WasmNativeAsset)`, so this can be removed.
.. dotnet.wasm . It defaults to `true`.
This is essentially #48500 minus the renaming of public items/properties. |
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for separating this out. Added some minor comments but I'm ok with it landing as is.
This PR is important to fast track in order to help alleviate longer helix wasm runs. |
Allow skipping AOT, per assembly with %(_InternalForceInterpret) metadata
new
$(WasmNativeDebugSymbols)
to control symbols fordotnet.wasm
(useful only for AOT case), which defaults to truePath handling fixes for AOT builds on windows
add create-packs.proj for setting up packs from a local build, for quick local testing
Also, note that this changes the default
$(AOTMode)
toAotInterp