Skip to content
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] simplify startup configuration #61072

Merged
merged 2 commits into from
Nov 3, 2021

Conversation

pavelsavara
Copy link
Member

@pavelsavara pavelsavara commented Nov 1, 2021

  • added Module.configSrc - to configure path to MonoConfig json file
  • added Module.onConfigLoaded callback
  • added Module.onDotNetReady replacing MonoConfig.loaded_cb
  • removed loaded_cb, assembly_list, runtime_assets, runtime_asset_sources from MonoConfig
  • simplified all sample and test projects
  • renamed Module.no_global_exports to Module.disableDotNet6Compatibility
  • implement default Module.preInit and Module.onRuntimeInitialized which could be overridden by user code (like Blazor)

@ghost
Copy link

ghost commented Nov 1, 2021

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details
  • added configSrc - path to MonoConfig json file
  • added Module.onConfigLoaded callback
  • added Module.onDotNetReady replacing MonoConfig.loaded_cb
  • removed loaded_cb, assembly_list, runtime_assets, runtime_asset_sources from MonoConfig
  • simplified all sample and test projects
  • renamed Module.no_global_exports to Module.disable6Compatibility
  • implement default Module.preInit and Module.onRuntimeInitialized which could be overridden by user code (like Blazor)
Author: pavelsavara
Assignees: -
Labels:

arch-wasm, area-System.Runtime.InteropServices.JavaScript

Milestone: 7.0.0

@pavelsavara pavelsavara requested a review from kg November 2, 2021 06:16
src/mono/wasm/runtime/exports.ts Outdated Show resolved Hide resolved
src/mono/wasm/runtime/startup.ts Outdated Show resolved Hide resolved
@lewing
Copy link
Member

lewing commented Nov 2, 2021

@steveisok we need a way to test changes like this in pr without directly fiddling with the yml. I think we should probably turn back on the interpreter lane until we have a way to trigger this

cc @marek-safar

@steveisok
Copy link
Member

steveisok commented Nov 2, 2021

I don't have a problem if you want to enable the interp lane until there's an option to manually trigger everything.

Remove $(_runSmokeTestsOnlyArg) from

buildArgs: -s mono+libs+host+packs+libs.tests -c $(_BuildConfig) /p:ArchiveTests=true $(_runSmokeTestsOnlyArg)
as part of this PR and it'll be enabled.

* added Module.onConfigLoaded callback
* added Module.onDotNetReady replacing MonoConfig.loaded_cb
* removed loaded_cb, assembly_list, runtime_assets, runtime_asset_sources from MonoConfig
* simplified all sample and test projects
* renamed no_global_exports to disableDotNet6Compatibility
* implement default Module.preInit and Module.onRuntimeInitialized which could be overriden by user code (like Blazor)
@pavelsavara pavelsavara merged commit 3950381 into dotnet:main Nov 3, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2021
@pavelsavara pavelsavara deleted the wasm_load_config branch January 4, 2022 13:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants