-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[browser] fix WasmProfilers vs WasmPerfTracing warning #115727
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
Conversation
Tagging subscribers to 'arch-wasm': @lewing |
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.
Pull Request Overview
This PR moves the WasmProfilers vs WasmPerfTracing/WasmPerfInstrumentation error checks from BrowserWasmApp.targets into the common targets file and adjusts the error messaging accordingly.
- Moved duplicated error validations from BrowserWasmApp.targets.
- Added or updated error conditions in WasmApp.Common.targets to standardize the behavior.
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
File | Description |
---|---|
src/mono/wasm/build/WasmApp.Common.targets | Added error conditions for incompatible WasmProfilers settings. |
src/mono/browser/build/BrowserWasmApp.targets | Removed redundant error conditions. |
/ba-g CI timeout |
_GetWasmGenerateAppBundleDependencies
only works in-tree