Skip to content

[browser-wasm] Support Mono runtime components in workload #54565

Closed

Description

@lambdageek

The browser-wasm workload should support selecting different mono runtime components (#50862) for different configurations.

This depends on #54417

Activity

  1. ghost added
    untriagedNew issue has not been triaged by the area owner
    on Jun 22, 2021
  2. added
    arch-wasmWebAssembly architecture
    and removed
    untriagedNew issue has not been triaged by the area owner
    on Jun 22, 2021
  3. added this to the 6.0.0 milestone on Jun 22, 2021
  4. radical commented on Jun 23, 2021

    @radical
    Member

    From Wasm targets pov, they will get a list of files to link for dotnet.js/wasm?

  5. lambdageek commented on Jun 23, 2021

    @lambdageek
    MemberAuthor

    From Wasm targets pov, they will get a list of files to link for dotnet.js/wasm?

    The workflow will be the same for all workloads:

    1. Populate @(_MonoComponents) with the components you want for example "" or "hot_reload;diagnostics_tracing" or "hot_reload" etc
    2. Call the _MonoSelectRuntimeComponents target at the appropriate time in your build
    3. Combine @(_MonoRuntimeComponentLink) with the full path of the native/ directory of your runtime pack and link those libraries together with libmonosgen-2.0.a when building your host.
    4. You now have an app bundle with components (or component stubs, depending on what you chose)
  6. lewing commented on Jul 14, 2021

    @lewing
    Member

    now is that #54432 is in we need to follow up here

  7. ghost locked as resolved and limited conversation to collaborators on Aug 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions