-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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] Improve AOT builds #48718
[wasm] Improve AOT builds #48718
Conversation
- The reason for this change is that generating the app bundle is optional now. Eg. in case of blazor, which handles the layout itself. - In that case, the assemblies will be used for other things during `WasmBuildApp` target (eg. AOT). - Change the name to reflect that
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.
This fixes emcc invocations with paths that have spaces (common on windows!).
Tagging subscribers to this area: @directhex Issue Details
|
This extracts changes from #48500 except the assembly skipping part. |
@@ -12,24 +12,24 @@ various properties before the target `WasmBuildApp` gets executed. | |||
to do that. | |||
|
|||
- By default, the `WasmLoadAssembliesAndReferences` task is not run, and | |||
the specified `@(WasmAssembliesToBundle)` are directly passed to | |||
the specified `@(WasmAssembly)` are directly passed to |
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.
WasmAOTAssembly? WasmAssembly feels very non-specific.
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.
they are not AOT specific
Co-authored-by: Pranav K <prkrishn@hotmail.com>
emcc
invocations, to work better with paths containing spaces