-
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
[build] Use MonoWasmBuildVariant to select runtime variant #80024
[build] Use MonoWasmBuildVariant to select runtime variant #80024
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsUse Note that this is distinct from what users do: the public The only tricky bit is that when building and testing the sample projects, we need to set the public properties, not the wasm build variant property. Fixes #75152
|
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
LGTM,
I'm just thinking whether MonoWasmRuntimeVariant
wouldn't be a better name?
We can consider changing in a follow-up PR. ( |
I'm going to pick up the changes in |
Use `MonoWasmBuildVariant=multithread` and `MonoWasmBuildVariant=perftrace` consistently to select the runtime variant. Previously we also supported setting `WasmEnableThreads` or `WasmEnablePerfTracing` to configure the runtime variant. This PR removes support for that. Note that this is distinct from what users do: the public `WasmEnableThreads` (respectively, `WasmEnablePerfTracing`) property are used in user project to choose the threaded (respectively, diagnostic tracing) runtime pack in a user project. That support is not going way in this PR. The only tricky bit is that when building and testing the sample projects, we need to set the public properties, not the wasm build variant property. Fixes dotnet#75152
bc8b531
to
ebd2ba7
Compare
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Use
MonoWasmBuildVariant=multithread
andMonoWasmBuildVariant=perftrace
consistently to select the runtime variant. Previously we also supported settingWasmEnableThreads
orWasmEnablePerfTracing
to configure the runtime variant. This PR removes support for that.Note that this is distinct from what users do: the public
WasmEnableThreads
(respectively,WasmEnablePerfTracing
) property are used in user project to choose the threaded (respectively, diagnostic tracing) runtime pack in a user project. That support is not going way in this PR.The only tricky bit is that when building and testing the sample projects, we need to set the public properties, not the wasm build variant property.
Fixes #75152